[
https://issues.apache.org/jira/browse/CURATOR-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15294148#comment-15294148
]
ASF GitHub Bot commented on CURATOR-308:
----------------------------------------
GitHub user Randgalt opened a pull request:
https://github.com/apache/curator/pull/149
[CURATOR-308] Parent container deletions could cause a hang
Parent container deletions could cause a hang as the watcher would never
fire. If parent containers get deleted now, reset and recreate them
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/curator CURATOR-308
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/curator/pull/149.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 #149
----
commit 9261ee622e2e2dd7b16969561cb597712f078acd
Author: randgalt <[email protected]>
Date: 2016-05-20T20:39:36Z
Parent container deletions could cause a hang as the watcher would never
fire. If parent containers get deleted now, reset and recreate them
----
> SimpleDistributedQueue::take() hangs if container nodes are removed
> -------------------------------------------------------------------
>
> Key: CURATOR-308
> URL: https://issues.apache.org/jira/browse/CURATOR-308
> Project: Apache Curator
> Issue Type: Bug
> Components: Recipes
> Affects Versions: 3.1.0
> Environment: org.apache.curator:curator-recipes 3.1.0
> org.apache.curator:curator-test 3.1.0
> Reporter: Philip Searle
> Assignee: Jordan Zimmerman
> Fix For: 3.1.1
>
> Attachments: TestSimpleDistributedQueueHang.java
>
>
> SimpleDistributedQueue creates the queue using container nodes if the
> ZooKeeper instance supports this feature. If ZooKeeper runs the container
> node cleanup task while SimpleDistributedQueue::take() is blocking, the call
> will not ever return.
> A similar issue occurs when calling poll(), resulting in it delaying until
> the timeout has elapsed, even if a queue item was inserted after the
> container cleanup occurs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
