You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@curator.apache.org by "Cameron McKenzie (JIRA)" <ji...@apache.org> on 2018/04/30 01:54:00 UTC

[jira] [Closed] (CURATOR-462) InterProcessSemaphoreV2 leaves orphaned lease node if acquiring the semaphore is interrupted at the wrong time

     [ https://issues.apache.org/jira/browse/CURATOR-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cameron McKenzie closed CURATOR-462.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 4.0.2

> InterProcessSemaphoreV2 leaves orphaned lease node if acquiring the semaphore is interrupted at the wrong time
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: CURATOR-462
>                 URL: https://issues.apache.org/jira/browse/CURATOR-462
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Recipes
>    Affects Versions: 2.11.0, 3.2.0, 3.2.1, 2.11.1, 3.3.0, 2.12.0, 4.0.0, 4.0.1
>            Reporter: Gergely Krajcsovszki
>            Priority: Major
>             Fix For: 4.0.2
>
>
> Since CURATOR-315, lease nodes created in org.apache.curator.framework.recipes.locks.InterProcessSemaphoreV2.internalAcquire1Lease(Builder<Lease>, long, boolean, long) are not returned if the wait for them to become active is interrupted. This is because the lease node is now only added to the builder at the end of the method, so the caller doesn't know about this node and cannot close it when catching an exception.
> We have already fixed this locally in our own dependent library so I'll make a PR with our fix and a test soon. We are still on the 2.x branch so we'd like if this fix could be in 2.13.0.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)