You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by Randgalt <gi...@git.apache.org> on 2016/06/02 22:28:22 UTC

[GitHub] curator pull request #155: [CURATOR-335] InterProcessSemaphoreV2 can deadloc...

GitHub user Randgalt opened a pull request:

    https://github.com/apache/curator/pull/155

    [CURATOR-335] InterProcessSemaphoreV2 can deadlock under network stress

    If there is a network event after the semaphore's node is created but before getChildren() is called, the previous implementation would orphan the newly created node causing a deadlock later on

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/apache/curator CURATOR-335

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/curator/pull/155.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #155
    
----

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] curator pull request #155: [CURATOR-335] InterProcessSemaphoreV2 can deadloc...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/curator/pull/155


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---