You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: