[jira] [Updated] (CURATOR-84) More flexibility for InterProcessMutex extensions

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

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

Jordan Zimmerman updated CURATOR-84:
------------------------------------

    Assignee: Cameron McKenzie

> More flexibility for InterProcessMutex extensions
> -------------------------------------------------
>
>                 Key: CURATOR-84
>                 URL: https://issues.apache.org/jira/browse/CURATOR-84
>             Project: Apache Curator
>          Issue Type: Wish
>          Components: Recipes
>    Affects Versions: 2.3.0
>            Reporter: Jozef Vilcek
>            Assignee: Cameron McKenzie
>             Fix For: 2.7.0
>
>         Attachments: CURATOR-84.patch
>
>
> I have a need for a durable InterProcessMutex. Main reason for this are processes with critical sections, where I can not afford to loose a lock due to session expiration. In such case, others might acquire a lock and kick in while the previous process is still running but e.g. experiencing connection issues. To kill this temporally detached process in favor of others would be too costly.
> To achieve such behavior, I need lock nodes to be created in PERSISTENT mode. This is not possible to do easily with currently implementation of locks due to few internal scoped classes and methods. I would like to change this.



--
This message was sent by Atlassian JIRA
(v6.2#6252)