Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

etcd client keeps the connection with a node which can not connect to leader. #8308

Closed
abel-von opened this issue Jul 26, 2017 · 1 comment
Closed
Milestone

Comments

@abel-von
Copy link

abel-von commented Jul 26, 2017

We are doing the HA test, and we found that when we cut the network connection between between an etcd instance and the leader, the etcd client do not close the connection with that instance. and all request will return a grpc timeout error.

I know that the etcd client will keep using a long live connection with one node of the cluster to send its request, until the connection is closed, by network partition or when the node stopped. but any etcd error will not make the client close the connection by its own.

I think maybe we can change the code to check the error, by some of the errors (like the grpc timeout error), we can close the connection and retry to request to other nodes.

@gyuho
Copy link
Contributor

gyuho commented Oct 6, 2017

Superseded by #8660.

@gyuho gyuho closed this as completed Oct 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants