jira-importer commented on issue #549: URL: https://github.com/apache/curator/issues/549#issuecomment-2604694578
<i><a href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=3l3ph4n1n3";>3l3ph4n1n3</a>:</i> <p>My problem is that a single client shouldn't be trusted to unlock the lock itself - the point of this failsafe is to ensure a system doesn't grind to a halt when a single client fails. There are many ways a client's lockTimer could fail yet the client's heartbeating to the zookeeper cluster continued - e.g. if the lockTimer thread had a bug in it and crashed, or deadlocked itself with another thread. Ideally the remaining clients would decide a bit later that the lock's lease time had expired, forcefully release the lock from the broken client and then one of them would acquire lock itself.</p> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@curator.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
