-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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_debugging_mvcc_keys_total inconsistency #8388
Comments
Maybe it's somehow connected with my old issue #8146, which is fixed now. |
@mwf can this be reproduced with master? |
Actually, I did not find a way to reproduce it, the issue is too strange to be true, but it's a fact :) I'll try, if I manage to reproduce I will let you know. But if you could take a look at code producing this metric value and maybe find a bug - that would be great. Just as you did in #8146. |
heyitsanthony
pushed a commit
to heyitsanthony/etcd
that referenced
this issue
Aug 10, 2017
gyuho
pushed a commit
that referenced
this issue
Aug 10, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue is connected with #8387
After the cluster stabilized we have inconsistency in "etcd_debugging_mvcc_keys_total" metric between hosts:
One host reports it has 15007 keys.
Though range request
ETCDCTL_API=3 etcdctl --endpoints="http://<host3>:2379" get --prefix --keys-only --limit=1 -w=json ""
tells it has only"count":7671
keys, which is the same as other hosts report in metrics.Maybe this issue was already fixed in newer etcd server versions? I just decided to report.
The text was updated successfully, but these errors were encountered: