[
https://issues.apache.org/jira/browse/CURATOR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14100745#comment-14100745
]
ASF GitHub Bot commented on CURATOR-84:
---------------------------------------
Github user jojovilco commented on the pull request:
https://github.com/apache/curator/pull/38#issuecomment-52509901
Wow, thanks a lot for pushing this forward!
I planed to put an enhancement into original path, but got stuck up with
other things.
In InterProcessMutext, I would love to have a (public / protected) method
which can returned a path to an actually owned lock znode (LockData.lockPath)
of a current thread. This would enable to build a pattern over a lock which
could guard for the case of lost lock and initiate an abort of currently
running task.
What do you think?
> 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)
