com.twitter.common.zookeeper.DistributedLockImpl tryLock does not cleanup after timeout #99

fracko opened this Issue Nov 8, 2012 · 1 comment


None yet

2 participants

fracko commented Nov 8, 2012

I try to use method tryLock. As I understand this method should try to acquire a lock for some time and if it this operation fails(because lock is already acquired) it returns false. What I've noticed is that even after unsuccessful lock acquire its locking node stays.

Can't we remove the node and clean the data after timeout?


I'm also seeing this behavior - is this a confirmed issue that will get fixed?

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