Skip to content
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

bug in WatchTree for etcd #166

Open
spacejam opened this issue Jun 12, 2017 · 0 comments
Open

bug in WatchTree for etcd #166

spacejam opened this issue Jun 12, 2017 · 0 comments

Comments

@spacejam
Copy link

WatchTree uses List on the target directory after receiving a watch event from the etcd client. There is no guarantee that the server that receives the later List request is the same one that triggered the previous Watch event. If the one that receives the List event is behind in the raft replication stream, the WatchTree chan will return an unchanged set of KVPair's. This can be fixed by either sending the List to the same server, or ensuring that whatever server receives the List command has a raft index >= the server that sent the Watch update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant