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

ZooKeeperProxy should not try to maintain canoncial versions of znodes #26

Open
stephentu opened this issue Sep 24, 2010 · 1 comment
Open

Comments

@stephentu
Copy link
Member

ZooKeeperProxy should not use the canonical map to pool znodes- since zookeeper watch semantics are "one time only", it is very difficult for the canonical map to be accurately updated when deletes from other clients are issued. this can cause many subtle bugs. since zookeeper's API allows us to explicit pass Watcher classes, we should instead use this feature for any watch callbacks we want to register

@marmbrus
Copy link
Member

Yeah, you are right. I don't think zookeeper had the ability to provide different watchers before (or I didn't know about it). Given that that infrastructure already exists in the java client we should just use it.

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

No branches or pull requests

2 participants