curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-84) More flexibility for InterProcessMutex extensions
Date Sat, 16 Aug 2014 17:15:18 GMT

    [ https://issues.apache.org/jira/browse/CURATOR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14099715#comment-14099715
] 

ASF GitHub Bot commented on CURATOR-84:
---------------------------------------

GitHub user karkum opened a pull request:

    https://github.com/apache/curator/pull/38

    CURATOR-84 More flexibility for InterProcessMutex extensions

    Credit goes to Jozef Vilcek for the initial patch. I just created a PR from the original
patch he had created.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/karkum/curator CURATOR-84

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/curator/pull/38.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #38
    
----
commit f6c4ede47ff1cf0748d4a2418218ba8d68e4aeef
Author: Karthik Kumar <karthik.kumar@opower.com>
Date:   2014-08-16T17:11:54Z

    CURATOR-84 More flexibility for InterProcessMutex extensions

----


> 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
>         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)

Mime
View raw message