jira-importer commented on issue #549: URL: https://github.com/apache/curator/issues/549#issuecomment-2604694608
<i><a href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=3l3ph4n1n3";>3l3ph4n1n3</a>:</i> <p>It's indeed cautious - but I really don't want my distributed locks to have a single point of failure (as you can't guarantee clients don't have bugs).</p> <p>Some more examples here - <a href="https://en.wikipedia.org/wiki/Lease_%28computer_science%29#Motivation"; class="external-link" target="_blank" rel="nofollow noopener">https://en.wikipedia.org/wiki/Lease_%28computer_science%29#Motivation</a> - and I've seen a client throw NoClassDefFoundErrors at runtime as one of the jars on its classpath was temporarily unreachable as it was on a networked file system!</p> <p>If I submitted a patch that (optionally) made all the clients attempt to delete a lock node after a fixed (but configurable) amount of time, would you consider including it? It'd remove the single point of failure (as any client can release the lock after the timeout, not just the one that took it), and this kind of functionality would ideally be part of the library anyway (to prevent applications that need it from writing pretty much the same code every time).</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
