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 3DE4B17332 for ; Wed, 1 Apr 2015 03:37:53 +0000 (UTC) Received: (qmail 37146 invoked by uid 500); 1 Apr 2015 03:37:53 -0000 Delivered-To: apmail-curator-dev-archive@curator.apache.org Received: (qmail 37105 invoked by uid 500); 1 Apr 2015 03:37:53 -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 37028 invoked by uid 99); 1 Apr 2015 03:37:52 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2015 03:37:52 +0000 Date: Wed, 1 Apr 2015 03:37:52 +0000 (UTC) From: "Jordan Zimmerman (JIRA)" To: dev@curator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CURATOR-173) InterProcessSemaphoreV2 nodes not reapable 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-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389938#comment-14389938 ] Jordan Zimmerman commented on CURATOR-173: ------------------------------------------ Please close then :) > InterProcessSemaphoreV2 nodes not reapable > ------------------------------------------ > > Key: CURATOR-173 > URL: https://issues.apache.org/jira/browse/CURATOR-173 > Project: Apache Curator > Issue Type: Bug > Reporter: David Kesler > Assignee: Scott Blum > Fix For: 2.7.2 > > > The curator documentation recommends using a reaper or childreaper to clean up stale lock nodes. This worked for InterProcessSemaphore locks. However lock paths that are created by InterProcessSemaphoreV2 cannot be reaped. The V2 recipe creates two subnodes beneath the lock node, 'locks' and 'leases', which are never cleaned up by the recipe. This ensures that the lock node itself will never be empty and thus never reaped. It doesn't seem like there's any safe way of handling cleaning up after an InterProcessSemaphoreV2 using canonical curator recipes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)