We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Number of keys keeps growing to absurd numbers, due to no delete requests.
Average of keys to be kept around 10 keys, the intention of the current logic was:
Expect it might a bug with nonUniqueWriteLimiter.
n/a
No response
main branch
TestRobustnessExploratory_Kubernetes_HighTraffic_ClusterOfSize3 test
$ etcdctl member list -w table # paste output here $ etcdctl --endpoints=<member list> endpoint status -w table # paste output here
The text was updated successfully, but these errors were encountered:
@serathius I can try to tackle this issue!
/assign @henrybear327
Sorry, something went wrong.
henrybear327
No branches or pull requests
Bug report criteria
What happened?
Number of keys keeps growing to absurd numbers, due to no delete requests.
What did you expect to happen?
Average of keys to be kept around 10 keys, the intention of the current logic was:
Expect it might a bug with nonUniqueWriteLimiter.
How can we reproduce it (as minimally and precisely as possible)?
n/a
Anything else we need to know?
No response
Etcd version (please run commands below)
main branch
Etcd configuration (command line flags or environment variables)
TestRobustnessExploratory_Kubernetes_HighTraffic_ClusterOfSize3 test
Etcd debug information (please run commands below, feel free to obfuscate the IP address or FQDN in the output)
Relevant log output
No response
The text was updated successfully, but these errors were encountered: