-
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
Lock.acquire throws NoNodeError #563
Comments
Hi, What do you have on your Zookeeper server logs? |
Is it possible this is a result of race conditions? Because Kazoo doesn't yet (i think) support Container nodes, it's nice to clean up a lock's parent node:
But I wonder if multiple clients contending for the same lock can cause problems in the case that Line 216 in 88b657a
but BEFORE Line 225 in 88b657a
Here's a test where I try to simulate that and got the
could consider catching Line 225 in 88b657a
I might be totally off tho. |
Same race-condition referenced in #329 |
We're seeing in our stack traces that a
NoNodeError
is thrown herekazoo/kazoo/recipe/lock.py
Line 225 in 88b657a
kazoo/kazoo/recipe/lock.py
Line 216 in 88b657a
Not sure if this is a client bug or a server bug
The text was updated successfully, but these errors were encountered: