-
Notifications
You must be signed in to change notification settings - Fork 38.6k
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
Add Etcd client support: stop traffic to in-defragmentation-server #124763
Comments
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/sig api-machinery |
What would you like to be added?
Etcd defragmentation is the workflow to prevent etcd from running out of disk space.
It is expected that defragmentation will result in timeouts and latency to requests that happen to be connected to the node being defragmented.
There is a proposal to stop traffic sending to being-defragmented-etcd-node.
etcd-io/etcd#16278
The Etcd server's implementation has been merged in etcd-io/etcd#17914, which is guarded by a feature flag.
Propose client side make the corresponding change (which can be guarded by feature flag as well) to complete the implementation.
Why is this needed?
This work will largely mitigate the Etcd defrag impact, decreasing the 5xx error rate.
to address the reported issue: #93280
The text was updated successfully, but these errors were encountered: