curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Kesler (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CURATOR-173) InterProcessSemaphoreV2 nodes not reapable
Date Mon, 22 Dec 2014 19:31:13 GMT
David Kesler created CURATOR-173:
------------------------------------

             Summary: 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: Jordan Zimmerman


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)

Mime
View raw message