-
Notifications
You must be signed in to change notification settings - Fork 387
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
Cleanup lock paths #329
Labels
Comments
It seems fine with me, wanna do a PR? |
maximilize
pushed a commit
to maximilize/kazoo
that referenced
this issue
May 29, 2015
maximilize
pushed a commit
to maximilize/kazoo
that referenced
this issue
Jun 17, 2015
btw this might be obsoleted by #334, depending on if you want to support older versions of ZK. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are using the lock recipe for millions of objects so we have to create a unique lock name for each object. Since the lock recipe does not delete the path this will mess up zookeeper after a short time.
My suggestion is to have an option to try to delete the path after the lock is released. This can lead to race conditions between ensure_path and the ephemeral node creation so have to do more changes to the recipe.
What do you guys think? Is there another way we can prevent messing up zookeeper with our millions of different locks?
The text was updated successfully, but these errors were encountered: