curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-121) PathChildrenCache is throwing an InterruptedException when being closed
Date Sun, 20 Jul 2014 23:43:38 GMT

    [ https://issues.apache.org/jira/browse/CURATOR-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14068079#comment-14068079
] 

ASF GitHub Bot commented on CURATOR-121:
----------------------------------------

GitHub user Randgalt opened a pull request:

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

    CURATOR-121 - Modified exception handling on the operation queue

    Modified exception handling on the operation queue to ignore InterruptedException during
shutdown. Added additional unit test for this case.

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

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

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

    https://github.com/apache/curator/pull/18.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 #18
    
----
commit 51109813ebd3104b74181be26532c3692f41bb02
Author: Cam McKenzie <cammckenzie@apache.org>
Date:   2014-07-19T18:10:32Z

    CURATOR-121 - Modified exception handling on the operation queue to
    ignore InterruptedException during shutdown. Added additional unit test
    for this case.

----


> PathChildrenCache is throwing an InterruptedException when being closed
> -----------------------------------------------------------------------
>
>                 Key: CURATOR-121
>                 URL: https://issues.apache.org/jira/browse/CURATOR-121
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Recipes
>    Affects Versions: 2.5.0, 2.6.0
>            Reporter: Corey J. Nolet
>            Assignee: Cameron McKenzie
>            Priority: Critical
>
> I have a server which is using the PathChildrenCache with the LeaderSelector so that
I can keep track of changes in leadership for a particular znode. Upon closing the PathChildrenCache,
I intermittently receive an InterruptedException like the following:
> {code}
> java.lang.InterruptedException
> at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1038)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1326)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:282)
> at org.apache.curator.CuratorZookeeperClient.internalBlockUntilConnectedOrTimedOut(CuratorZookeeperClient.java:324)
> at org.apache.curator.RetryLoop.callWithRetry(RetryLoop.java:105)
> at org.apache.curator.utils.EnsurePath$InitialHelper.ensure(EnsurePath.java:140)
> at org.apache.curator.utils.EnsurePath.ensure(EnsurePath.java:99)
> at org.apache.curator.framework.recipes.cache.PathChildrenCache.refresh(PathChildrenCache.java:481)
> at org.apache.curator.framework.recipes.cache.RefreshOperation.invoke(RefreshOperation.java:35)
> at org.apache.curator.framework.recipes.cache.PathChildrenCache$10.run(PathChildrenCache.java:762)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:724)
> {code}
> It doesn't happen all the time but it does happen about 2-3 times in a test suite that's
creating and stopping the server about 60 times total.
> [~randgalt] mentioned on the mailing list that this may be a bug in the framework.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message