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

["Jordan Zimmerman (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CURATOR-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jordan Zimmerman updated CURATOR-465:
-------------------------------------
    Fix Version/s:     (was: 4.1.0)
                   TBD

> 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
>            Priority: Major
>             Fix For: TBD
>
>
> 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)