Repository navigation
Need for circuit breaker integration in ETCD client library #22367
shivam0891
started this conversation in
Ideas
Replies: 3 comments 1 reply
|
From community meeting, for me seems related to https://github.com/kubernetes/enhancements/pull/6319/changes |
0 replies
|
If we accept this, we should ensure it's more generic instead of a bespoken solution. Also if we support #22328, it should also resolve this case, but the concern on that one is that is uses grpc's experimental package. |
1 reply
|
Would love to learn more about how this is done (e.g., what threads/time windows do you use for circuit breaker), and how this can be done more natively, using existing grpc-go primitives |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi etcd-folks,
We have fleet size of 1500+ ETCD clusters and we have seen lot of issues due to 1 degraded node in ETCD(be it slow disk, stale follower, noisy neighbour, etcd in built rate limiter) due to lack of circuit breaker in ETCD client.
We have build the wrapper client and provided the circuit breaker to solve these issues and so far it is working fine. So i wanted to check the feasibility to add this capability to etcd client itself? so you see any concern in this?
All reactions