Skip to content

Just created key can be omitted #262

New issue
New issue
Open
Open
Just created key can be omitted#262

Description

@VadimPushtaev
VadimPushtaev
opened on May 16, 2018

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

Activity

  1. VadimPushtaev commented on May 16, 2018

    @VadimPushtaev
    VadimPushtaev
    on May 16, 2018
    Author

    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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions