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.

Sign up for GitHub

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

Jump to bottom

Just created key can be omitted #262

Open

VadimPushtaev opened this issue May 16, 2018 · 1 comment

VadimPushtaev commented May 16, 2018 •

edited

Loading

If you happen to create a key on some node X and immediately do recursive read on another node Y, it's entirely possible for the key not to be there.

python-etcd/src/etcd/lock.py

Line 176 in b227f49

# Something very wrong is going on, most probably

Author

VadimPushtaev commented May 16, 2018

As with all distributed systems, it is impossible for etcd to ensure strict consistency. etcd does not guarantee that it will return to a read the “most recent” value (as measured by a wall clock when a request is completed) available on any cluster member.

https://coreos.com/etcd/docs/latest/learning/api_guarantees.html#guarantees-provided

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment