[jira] [Resolved] (CURATOR-48) InterProcessSemaphoreMutex should use InterProcessSemaphoreV2

["Jordan Zimmerman (JIRA)" <ji...@apache.org>]

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

Jordan Zimmerman resolved CURATOR-48.
-------------------------------------

    Resolution: Fixed

InterProcessSemaphoreMutex changed to use InterProcessSemaphoreV2. In the process, a bug in InterProcessSemaphoreV2 was noticed that was been long fixed in the older InterProcessSemaphore. If the session drops in the process of creating the lock node, the acquire fails. The old InterProcessSemaphore worked around this by using a retry loop to try to recreate the lock node. InterProcessSemaphoreV2 now does this as well.
    
Also, as part of this checkin, testWaitingProcessKilledServer has been tightened and made to be more reliable.
                
> InterProcessSemaphoreMutex should use InterProcessSemaphoreV2
> -------------------------------------------------------------
>
>                 Key: CURATOR-48
>                 URL: https://issues.apache.org/jira/browse/CURATOR-48
>             Project: Apache Curator
>          Issue Type: Improvement
>          Components: Recipes
>            Reporter: Jordan Zimmerman
>            Assignee: Jordan Zimmerman
>             Fix For: TBD
>
>
> InterProcessSemaphoreMutex currently uses InterProcessSemaphore which is deprecated. It should instead use InterProcessSemaphoreV2.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira