You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "Jordan Zimmerman (JIRA)" <ji...@apache.org> on 2018/04/25 23:42:00 UTC

[jira] [Created] (CURATOR-465) Curator needs an abstraction that interrupts locking threads when there are connection problems

Jordan Zimmerman created CURATOR-465:
----------------------------------------

             Summary: Curator needs an abstraction that interrupts locking threads when there are connection problems
                 Key: CURATOR-465
                 URL: https://issues.apache.org/jira/browse/CURATOR-465
             Project: Apache Curator
          Issue Type: Improvement
          Components: Framework, Recipes
    Affects Versions: 4.0.1
            Reporter: Jordan Zimmerman
             Fix For: 4.0.2


For some reason, we don't have an abstraction that manages interrupting a thread that's using one of Curator's lock recipes. Our docs say that if you get SUSPENDED/LOST you should interrupt any locks/leaders. {{LeaderSelectorListenerAdapter}} handles this but we don't have something for locks or {{LeaderLatch}}. 

I think something like the {{Locker}} class would work where when the lock is acquired, the current thread is recorded. The class adds a {{ConnectionStateListener}} and interrupts the thread when the connection is lost.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)