Return-Path: X-Original-To: apmail-curator-dev-archive@minotaur.apache.org Delivered-To: apmail-curator-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 09DD51124F for ; Tue, 26 Aug 2014 13:39:58 +0000 (UTC) Received: (qmail 94773 invoked by uid 500); 26 Aug 2014 13:39:57 -0000 Delivered-To: apmail-curator-dev-archive@curator.apache.org Received: (qmail 94727 invoked by uid 500); 26 Aug 2014 13:39:57 -0000 Mailing-List: contact dev-help@curator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@curator.apache.org Delivered-To: mailing list dev@curator.apache.org Received: (qmail 94715 invoked by uid 99); 26 Aug 2014 13:39:57 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Aug 2014 13:39:57 +0000 Date: Tue, 26 Aug 2014 13:39:57 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: dev@curator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CURATOR-84) More flexibility for InterProcessMutex extensions MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CURATOR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14110699#comment-14110699 ] ASF GitHub Bot commented on CURATOR-84: --------------------------------------- Github user karkum commented on the pull request: https://github.com/apache/curator/pull/38#issuecomment-53421096 @Randgalt, have you had a chance to look over this again? > 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)