[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close
[
https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14077679#comment-14077679
]
ASF GitHub Bot commented on CURATOR-126:
Github user asfgit closed the pull request at:
https://github.com/apache/curator/pull/23
IllegalStateException in performBackgroundOperation during close
Key: CURATOR-126
URL: https://issues.apache.org/jira/browse/CURATOR-126
Project: Apache Curator
Issue Type: Bug
Components: Framework
Affects Versions: 2.5.0
Reporter: Scott Blum
Assignee: Jordan Zimmerman
Fix For: 2.7.0
Original Estimate: 24h
Remaining Estimate: 24h
{code}
[CuratorFramework-0] ERROR
org.apache.curator.framework.imps.CuratorFrameworkImpl - Background
exception was not retry-able or retry gave up
java.lang.IllegalStateException: Client is not started
at
com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at
org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:807)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:793)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.access$400(CuratorFrameworkImpl.java:57)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:275)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
{code}
I see this sometimes during test runs; I believe this happens because
CuratorZookeeperClient.started gets set to false during shutdown, but the
backgroundOperation loop can still be running since shutting down the
backgroundOperation loop is inherently racy.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close
[
https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14075935#comment-14075935
]
Cameron McKenzie commented on CURATOR-126:
--
I've had a bit of a look at this and have a unit test to reproduce the issue.
It would seem that (unless I'm missing something), it would be simplest just to
shutdown the executor thread before the ZooKeeper client is closed.
In the CuratorFrameworkImpl method, this:
client.close();
namespaceWatcherMap.close();
if ( executorService != null )
{
executorService.shutdownNow();
}
would be changed to:
namespaceWatcherMap.close();
if ( executorService != null )
{
executorService.shutdownNow();
}
client.close();
IllegalStateException in performBackgroundOperation during close
Key: CURATOR-126
URL: https://issues.apache.org/jira/browse/CURATOR-126
Project: Apache Curator
Issue Type: Bug
Components: Framework
Affects Versions: 2.5.0
Reporter: Scott Blum
Assignee: Cameron McKenzie
Original Estimate: 24h
Remaining Estimate: 24h
{code}
[CuratorFramework-0] ERROR
org.apache.curator.framework.imps.CuratorFrameworkImpl - Background
exception was not retry-able or retry gave up
java.lang.IllegalStateException: Client is not started
at
com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at
org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:807)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:793)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.access$400(CuratorFrameworkImpl.java:57)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:275)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
{code}
I see this sometimes during test runs; I believe this happens because
CuratorZookeeperClient.started gets set to false during shutdown, but the
backgroundOperation loop can still be running since shutting down the
backgroundOperation loop is inherently racy.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close
[
https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14076204#comment-14076204
]
Jordan Zimmerman commented on CURATOR-126:
--
I think the above change is a good idea, but it probably won't totally solve
the problem. executorService.shutdownNow() will just interrupt the threads and,
so, the client will still get closed while a background thread is executing.
We could consider calling executorService.awaitTermination() but that would be
a significant change.
IllegalStateException in performBackgroundOperation during close
Key: CURATOR-126
URL: https://issues.apache.org/jira/browse/CURATOR-126
Project: Apache Curator
Issue Type: Bug
Components: Framework
Affects Versions: 2.5.0
Reporter: Scott Blum
Assignee: Cameron McKenzie
Original Estimate: 24h
Remaining Estimate: 24h
{code}
[CuratorFramework-0] ERROR
org.apache.curator.framework.imps.CuratorFrameworkImpl - Background
exception was not retry-able or retry gave up
java.lang.IllegalStateException: Client is not started
at
com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at
org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:807)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:793)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.access$400(CuratorFrameworkImpl.java:57)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:275)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
{code}
I see this sometimes during test runs; I believe this happens because
CuratorZookeeperClient.started gets set to false during shutdown, but the
backgroundOperation loop can still be running since shutting down the
backgroundOperation loop is inherently racy.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close
[
https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14076460#comment-14076460
]
Jordan Zimmerman commented on CURATOR-126:
--
An Executor is just a thread as well. I'm not sure how changing to a Thread
would help.
IllegalStateException in performBackgroundOperation during close
Key: CURATOR-126
URL: https://issues.apache.org/jira/browse/CURATOR-126
Project: Apache Curator
Issue Type: Bug
Components: Framework
Affects Versions: 2.5.0
Reporter: Scott Blum
Assignee: Cameron McKenzie
Original Estimate: 24h
Remaining Estimate: 24h
{code}
[CuratorFramework-0] ERROR
org.apache.curator.framework.imps.CuratorFrameworkImpl - Background
exception was not retry-able or retry gave up
java.lang.IllegalStateException: Client is not started
at
com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at
org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:807)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:793)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.access$400(CuratorFrameworkImpl.java:57)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:275)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
{code}
I see this sometimes during test runs; I believe this happens because
CuratorZookeeperClient.started gets set to false during shutdown, but the
backgroundOperation loop can still be running since shutting down the
backgroundOperation loop is inherently racy.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close
[
https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14076457#comment-14076457
]
Scott Blum commented on CURATOR-126:
Also, versions of Java 1.8 have a bug in FutureTask.cancel() where the *wrong
thread* will sometimes get interrupted (and that's the underlying thing that
happens when you call Executor.shutdownNow()).
IllegalStateException in performBackgroundOperation during close
Key: CURATOR-126
URL: https://issues.apache.org/jira/browse/CURATOR-126
Project: Apache Curator
Issue Type: Bug
Components: Framework
Affects Versions: 2.5.0
Reporter: Scott Blum
Assignee: Cameron McKenzie
Original Estimate: 24h
Remaining Estimate: 24h
{code}
[CuratorFramework-0] ERROR
org.apache.curator.framework.imps.CuratorFrameworkImpl - Background
exception was not retry-able or retry gave up
java.lang.IllegalStateException: Client is not started
at
com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at
org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:807)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:793)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.access$400(CuratorFrameworkImpl.java:57)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:275)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
{code}
I see this sometimes during test runs; I believe this happens because
CuratorZookeeperClient.started gets set to false during shutdown, but the
backgroundOperation loop can still be running since shutting down the
backgroundOperation loop is inherently racy.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close
[
https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14076576#comment-14076576
]
Scott Blum commented on CURATOR-126:
You're right, Thread.interrupt(), Thread.join() is almost identical to
Executor.shutdownNow(), Executor.awaitTermination() EXCEPT for the JDK bug
which affects Executor.shutdownNow().
http://bugs.java.com/bugdatabase/view_bug.do?bug_id=7132378
IllegalStateException in performBackgroundOperation during close
Key: CURATOR-126
URL: https://issues.apache.org/jira/browse/CURATOR-126
Project: Apache Curator
Issue Type: Bug
Components: Framework
Affects Versions: 2.5.0
Reporter: Scott Blum
Assignee: Cameron McKenzie
Original Estimate: 24h
Remaining Estimate: 24h
{code}
[CuratorFramework-0] ERROR
org.apache.curator.framework.imps.CuratorFrameworkImpl - Background
exception was not retry-able or retry gave up
java.lang.IllegalStateException: Client is not started
at
com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at
org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:807)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:793)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.access$400(CuratorFrameworkImpl.java:57)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:275)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
{code}
I see this sometimes during test runs; I believe this happens because
CuratorZookeeperClient.started gets set to false during shutdown, but the
backgroundOperation loop can still be running since shutting down the
backgroundOperation loop is inherently racy.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close
[
https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14076603#comment-14076603
]
ASF GitHub Bot commented on CURATOR-126:
Github user dragonsinth commented on a diff in the pull request:
https://github.com/apache/curator/pull/23#discussion_r15483096
--- Diff:
curator-framework/src/main/java/org/apache/curator/framework/imps/CuratorFrameworkImpl.java
---
@@ -722,39 +725,35 @@ public void retriesExhausted(OperationAndDataString
operationAndData)
private DATA_TYPE void
handleBackgroundOperationException(OperationAndDataDATA_TYPE
operationAndData, Throwable e)
{
-do
+if ( (operationAndData != null) RetryLoop.isRetryException(e) )
{
-if ( (operationAndData != null)
RetryLoop.isRetryException(e) )
+if (
!Boolean.getBoolean(DebugUtils.PROPERTY_DONT_LOG_CONNECTION_ISSUES) )
+{
+log.debug(Retry-able exception received, e);
+}
+if (
client.getRetryPolicy().allowRetry(operationAndData.getThenIncrementRetryCount(),
operationAndData.getElapsedTimeMs(), operationAndData) )
{
if (
!Boolean.getBoolean(DebugUtils.PROPERTY_DONT_LOG_CONNECTION_ISSUES) )
{
-log.debug(Retry-able exception received, e);
+log.debug(Retrying operation);
}
-if (
client.getRetryPolicy().allowRetry(operationAndData.getThenIncrementRetryCount(),
operationAndData.getElapsedTimeMs(), operationAndData) )
+backgroundOperations.offer(operationAndData);
+return;
+}
+else
+{
+if (
!Boolean.getBoolean(DebugUtils.PROPERTY_DONT_LOG_CONNECTION_ISSUES) )
{
-if (
!Boolean.getBoolean(DebugUtils.PROPERTY_DONT_LOG_CONNECTION_ISSUES) )
-{
-log.debug(Retrying operation);
-}
-backgroundOperations.offer(operationAndData);
-break;
+log.debug(Retry policy did not allow retry);
}
-else
+if ( operationAndData.getErrorCallback() != null )
{
-if (
!Boolean.getBoolean(DebugUtils.PROPERTY_DONT_LOG_CONNECTION_ISSUES) )
-{
-log.debug(Retry policy did not allow retry);
-}
-if ( operationAndData.getErrorCallback() != null )
-{
-
operationAndData.getErrorCallback().retriesExhausted(operationAndData);
-}
+
operationAndData.getErrorCallback().retriesExhausted(operationAndData);
}
}
-
-logError(Background exception was not retry-able or retry
gave up, e);
}
-while ( false );
+
+logError(Background exception was not retry-able or retry gave
up, e);
--- End diff --
This is unrelated to the main change. While I was in here, I noticed this
method was more complicated than it needed to be. I could revert this section
if you guys would prefer to isolate changes.
IllegalStateException in performBackgroundOperation during close
Key: CURATOR-126
URL: https://issues.apache.org/jira/browse/CURATOR-126
Project: Apache Curator
Issue Type: Bug
Components: Framework
Affects Versions: 2.5.0
Reporter: Scott Blum
Assignee: Cameron McKenzie
Original Estimate: 24h
Remaining Estimate: 24h
{code}
[CuratorFramework-0] ERROR
org.apache.curator.framework.imps.CuratorFrameworkImpl - Background
exception was not retry-able or retry gave up
java.lang.IllegalStateException: Client is not started
at
com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at
org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:807)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:793)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.access$400(CuratorFrameworkImpl.java:57)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:275)
at
[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close
[
https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14076610#comment-14076610
]
ASF GitHub Bot commented on CURATOR-126:
Github user dragonsinth commented on a diff in the pull request:
https://github.com/apache/curator/pull/23#discussion_r15483196
--- Diff:
curator-framework/src/main/java/org/apache/curator/framework/imps/CuratorFrameworkImpl.java
---
@@ -770,9 +769,8 @@ private void backgroundOperationsLoop()
debugListener.listen(operationAndData);
}
}
-catch ( InterruptedException e )
+catch ( InterruptedException ignored )
{
-Thread.currentThread().interrupt();
--- End diff --
not necessary; also inconsistent with the while condition. If the loop
exits because the while condition test reads the interrupted value, it's not
resetting the interrupted flag anyway, so there's no point doing it on this
exit path either.
IllegalStateException in performBackgroundOperation during close
Key: CURATOR-126
URL: https://issues.apache.org/jira/browse/CURATOR-126
Project: Apache Curator
Issue Type: Bug
Components: Framework
Affects Versions: 2.5.0
Reporter: Scott Blum
Assignee: Cameron McKenzie
Original Estimate: 24h
Remaining Estimate: 24h
{code}
[CuratorFramework-0] ERROR
org.apache.curator.framework.imps.CuratorFrameworkImpl - Background
exception was not retry-able or retry gave up
java.lang.IllegalStateException: Client is not started
at
com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at
org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:807)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:793)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.access$400(CuratorFrameworkImpl.java:57)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:275)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
{code}
I see this sometimes during test runs; I believe this happens because
CuratorZookeeperClient.started gets set to false during shutdown, but the
backgroundOperation loop can still be running since shutting down the
backgroundOperation loop is inherently racy.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close
[
https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14076617#comment-14076617
]
ASF GitHub Bot commented on CURATOR-126:
Github user dragonsinth commented on a diff in the pull request:
https://github.com/apache/curator/pull/23#discussion_r15483300
--- Diff:
curator-framework/src/main/java/org/apache/curator/framework/imps/CuratorFrameworkImpl.java
---
@@ -300,12 +295,20 @@ public Void apply(CuratorListener listener)
listeners.clear();
unhandledErrorListeners.clear();
connectionStateManager.close();
+if (backgroundThread != null) {
+backgroundThread.interrupt();
+try
+{
+backgroundThread.join(1000);
--- End diff --
I totally made this number up. What's the right thing here?
IllegalStateException in performBackgroundOperation during close
Key: CURATOR-126
URL: https://issues.apache.org/jira/browse/CURATOR-126
Project: Apache Curator
Issue Type: Bug
Components: Framework
Affects Versions: 2.5.0
Reporter: Scott Blum
Assignee: Cameron McKenzie
Original Estimate: 24h
Remaining Estimate: 24h
{code}
[CuratorFramework-0] ERROR
org.apache.curator.framework.imps.CuratorFrameworkImpl - Background
exception was not retry-able or retry gave up
java.lang.IllegalStateException: Client is not started
at
com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at
org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:807)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:793)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.access$400(CuratorFrameworkImpl.java:57)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:275)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
{code}
I see this sometimes during test runs; I believe this happens because
CuratorZookeeperClient.started gets set to false during shutdown, but the
backgroundOperation loop can still be running since shutting down the
backgroundOperation loop is inherently racy.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close
[
https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14076696#comment-14076696
]
ASF GitHub Bot commented on CURATOR-126:
Github user Randgalt commented on a diff in the pull request:
https://github.com/apache/curator/pull/23#discussion_r15485833
--- Diff:
curator-framework/src/main/java/org/apache/curator/framework/imps/CuratorFrameworkImpl.java
---
@@ -74,7 +71,7 @@
private final NamespaceFacadeCache namespaceFacadeCache;
private final NamespaceWatcherMap namespaceWatcherMap = new
NamespaceWatcherMap(this);
-private volatile ExecutorService executorService;
+private volatile Thread backgroundThread;
--- End diff --
I disagree with changing this to Thread. I understand that there are some
bugs with Executor but that's a much larger issues. Curator uses Executor
everywhere. If the Executor bug will exhibit here it will do so everywhere. We
can consider a global fix for the bug (which I don't yet understand).
IllegalStateException in performBackgroundOperation during close
Key: CURATOR-126
URL: https://issues.apache.org/jira/browse/CURATOR-126
Project: Apache Curator
Issue Type: Bug
Components: Framework
Affects Versions: 2.5.0
Reporter: Scott Blum
Assignee: Cameron McKenzie
Original Estimate: 24h
Remaining Estimate: 24h
{code}
[CuratorFramework-0] ERROR
org.apache.curator.framework.imps.CuratorFrameworkImpl - Background
exception was not retry-able or retry gave up
java.lang.IllegalStateException: Client is not started
at
com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at
org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:807)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:793)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.access$400(CuratorFrameworkImpl.java:57)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:275)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
{code}
I see this sometimes during test runs; I believe this happens because
CuratorZookeeperClient.started gets set to false during shutdown, but the
backgroundOperation loop can still be running since shutting down the
backgroundOperation loop is inherently racy.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close
[
https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14076701#comment-14076701
]
ASF GitHub Bot commented on CURATOR-126:
Github user dragonsinth commented on a diff in the pull request:
https://github.com/apache/curator/pull/23#discussion_r15485966
--- Diff:
curator-framework/src/main/java/org/apache/curator/framework/imps/CuratorFrameworkImpl.java
---
@@ -722,39 +725,35 @@ public void retriesExhausted(OperationAndDataString
operationAndData)
private DATA_TYPE void
handleBackgroundOperationException(OperationAndDataDATA_TYPE
operationAndData, Throwable e)
{
-do
+if ( (operationAndData != null) RetryLoop.isRetryException(e) )
{
-if ( (operationAndData != null)
RetryLoop.isRetryException(e) )
+if (
!Boolean.getBoolean(DebugUtils.PROPERTY_DONT_LOG_CONNECTION_ISSUES) )
+{
+log.debug(Retry-able exception received, e);
+}
+if (
client.getRetryPolicy().allowRetry(operationAndData.getThenIncrementRetryCount(),
operationAndData.getElapsedTimeMs(), operationAndData) )
{
if (
!Boolean.getBoolean(DebugUtils.PROPERTY_DONT_LOG_CONNECTION_ISSUES) )
{
-log.debug(Retry-able exception received, e);
+log.debug(Retrying operation);
}
-if (
client.getRetryPolicy().allowRetry(operationAndData.getThenIncrementRetryCount(),
operationAndData.getElapsedTimeMs(), operationAndData) )
+backgroundOperations.offer(operationAndData);
+return;
+}
+else
+{
+if (
!Boolean.getBoolean(DebugUtils.PROPERTY_DONT_LOG_CONNECTION_ISSUES) )
{
-if (
!Boolean.getBoolean(DebugUtils.PROPERTY_DONT_LOG_CONNECTION_ISSUES) )
-{
-log.debug(Retrying operation);
-}
-backgroundOperations.offer(operationAndData);
-break;
+log.debug(Retry policy did not allow retry);
}
-else
+if ( operationAndData.getErrorCallback() != null )
{
-if (
!Boolean.getBoolean(DebugUtils.PROPERTY_DONT_LOG_CONNECTION_ISSUES) )
-{
-log.debug(Retry policy did not allow retry);
-}
-if ( operationAndData.getErrorCallback() != null )
-{
-
operationAndData.getErrorCallback().retriesExhausted(operationAndData);
-}
+
operationAndData.getErrorCallback().retriesExhausted(operationAndData);
}
}
-
-logError(Background exception was not retry-able or retry
gave up, e);
}
-while ( false );
+
+logError(Background exception was not retry-able or retry gave
up, e);
--- End diff --
Sure thing.
IllegalStateException in performBackgroundOperation during close
Key: CURATOR-126
URL: https://issues.apache.org/jira/browse/CURATOR-126
Project: Apache Curator
Issue Type: Bug
Components: Framework
Affects Versions: 2.5.0
Reporter: Scott Blum
Assignee: Cameron McKenzie
Original Estimate: 24h
Remaining Estimate: 24h
{code}
[CuratorFramework-0] ERROR
org.apache.curator.framework.imps.CuratorFrameworkImpl - Background
exception was not retry-able or retry gave up
java.lang.IllegalStateException: Client is not started
at
com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at
org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:807)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:793)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.access$400(CuratorFrameworkImpl.java:57)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:275)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close
[
https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14076709#comment-14076709
]
ASF GitHub Bot commented on CURATOR-126:
Github user dragonsinth commented on a diff in the pull request:
https://github.com/apache/curator/pull/23#discussion_r15486219
--- Diff:
curator-framework/src/main/java/org/apache/curator/framework/imps/CuratorFrameworkImpl.java
---
@@ -770,9 +769,8 @@ private void backgroundOperationsLoop()
debugListener.listen(operationAndData);
}
}
-catch ( InterruptedException e )
+catch ( InterruptedException ignored )
{
-Thread.currentThread().interrupt();
--- End diff --
Let me be more clear. The way the loop is constructed:
```
private void backgroundOperationsLoop()
{
while ( !Thread.interrupted() )
{ ... }
```
ALREADY eats the interrupted status. Simply checking
`Thread.interrupted()` consumes it. If you want to consistently enforce a rule
that you always re-interrupt threads (which is a good rule in general, although
not necessary here) then you need an unconditional re-interrupt at the end of
the method.
Do you want me to add that?
My point is that putting the interrupt only in the catch block is
inconsistent. It re-interrupts in the case where an InterruptedException gets
throws, and fails to re-interrupt when the loop exits without exception.
IllegalStateException in performBackgroundOperation during close
Key: CURATOR-126
URL: https://issues.apache.org/jira/browse/CURATOR-126
Project: Apache Curator
Issue Type: Bug
Components: Framework
Affects Versions: 2.5.0
Reporter: Scott Blum
Assignee: Cameron McKenzie
Original Estimate: 24h
Remaining Estimate: 24h
{code}
[CuratorFramework-0] ERROR
org.apache.curator.framework.imps.CuratorFrameworkImpl - Background
exception was not retry-able or retry gave up
java.lang.IllegalStateException: Client is not started
at
com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at
org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:807)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:793)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.access$400(CuratorFrameworkImpl.java:57)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:275)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
{code}
I see this sometimes during test runs; I believe this happens because
CuratorZookeeperClient.started gets set to false during shutdown, but the
backgroundOperation loop can still be running since shutting down the
backgroundOperation loop is inherently racy.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close
[
https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14076715#comment-14076715
]
ASF GitHub Bot commented on CURATOR-126:
Github user Randgalt commented on a diff in the pull request:
https://github.com/apache/curator/pull/23#discussion_r15486333
--- Diff:
curator-framework/src/main/java/org/apache/curator/framework/imps/CuratorFrameworkImpl.java
---
@@ -770,9 +769,8 @@ private void backgroundOperationsLoop()
debugListener.listen(operationAndData);
}
}
-catch ( InterruptedException e )
+catch ( InterruptedException ignored )
{
-Thread.currentThread().interrupt();
--- End diff --
Actually, that's a bug! I didn't see it. It should be
Thread.currentThread().isInterrupted() which doesn't clear the state. Normally
I use that one. I'm going to greg the code for other instances of this.
IllegalStateException in performBackgroundOperation during close
Key: CURATOR-126
URL: https://issues.apache.org/jira/browse/CURATOR-126
Project: Apache Curator
Issue Type: Bug
Components: Framework
Affects Versions: 2.5.0
Reporter: Scott Blum
Assignee: Cameron McKenzie
Original Estimate: 24h
Remaining Estimate: 24h
{code}
[CuratorFramework-0] ERROR
org.apache.curator.framework.imps.CuratorFrameworkImpl - Background
exception was not retry-able or retry gave up
java.lang.IllegalStateException: Client is not started
at
com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at
org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:807)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:793)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.access$400(CuratorFrameworkImpl.java:57)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:275)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
{code}
I see this sometimes during test runs; I believe this happens because
CuratorZookeeperClient.started gets set to false during shutdown, but the
backgroundOperation loop can still be running since shutting down the
backgroundOperation loop is inherently racy.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close
[
https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14076718#comment-14076718
]
ASF GitHub Bot commented on CURATOR-126:
Github user Randgalt commented on a diff in the pull request:
https://github.com/apache/curator/pull/23#discussion_r15486439
--- Diff:
curator-framework/src/main/java/org/apache/curator/framework/imps/CuratorFrameworkImpl.java
---
@@ -770,9 +769,8 @@ private void backgroundOperationsLoop()
debugListener.listen(operationAndData);
}
}
-catch ( InterruptedException e )
+catch ( InterruptedException ignored )
{
-Thread.currentThread().interrupt();
--- End diff --
I just checked - that's the only instance of it in the code. If you don't
mind, please fix it as part of this PR.
IllegalStateException in performBackgroundOperation during close
Key: CURATOR-126
URL: https://issues.apache.org/jira/browse/CURATOR-126
Project: Apache Curator
Issue Type: Bug
Components: Framework
Affects Versions: 2.5.0
Reporter: Scott Blum
Assignee: Cameron McKenzie
Original Estimate: 24h
Remaining Estimate: 24h
{code}
[CuratorFramework-0] ERROR
org.apache.curator.framework.imps.CuratorFrameworkImpl - Background
exception was not retry-able or retry gave up
java.lang.IllegalStateException: Client is not started
at
com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at
org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:807)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:793)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.access$400(CuratorFrameworkImpl.java:57)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:275)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
{code}
I see this sometimes during test runs; I believe this happens because
CuratorZookeeperClient.started gets set to false during shutdown, but the
backgroundOperation loop can still be running since shutting down the
backgroundOperation loop is inherently racy.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close
[
https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14076736#comment-14076736
]
ASF GitHub Bot commented on CURATOR-126:
Github user dragonsinth commented on a diff in the pull request:
https://github.com/apache/curator/pull/23#discussion_r15487087
--- Diff:
curator-framework/src/main/java/org/apache/curator/framework/imps/CuratorFrameworkImpl.java
---
@@ -300,12 +295,20 @@ public Void apply(CuratorListener listener)
listeners.clear();
unhandledErrorListeners.clear();
connectionStateManager.close();
+if (backgroundThread != null) {
+backgroundThread.interrupt();
+try
+{
+backgroundThread.join(1000);
--- End diff --
Done. I set the default to 1 second, let me know if should be different.
IllegalStateException in performBackgroundOperation during close
Key: CURATOR-126
URL: https://issues.apache.org/jira/browse/CURATOR-126
Project: Apache Curator
Issue Type: Bug
Components: Framework
Affects Versions: 2.5.0
Reporter: Scott Blum
Assignee: Cameron McKenzie
Original Estimate: 24h
Remaining Estimate: 24h
{code}
[CuratorFramework-0] ERROR
org.apache.curator.framework.imps.CuratorFrameworkImpl - Background
exception was not retry-able or retry gave up
java.lang.IllegalStateException: Client is not started
at
com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at
org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:807)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:793)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.access$400(CuratorFrameworkImpl.java:57)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:275)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
{code}
I see this sometimes during test runs; I believe this happens because
CuratorZookeeperClient.started gets set to false during shutdown, but the
backgroundOperation loop can still be running since shutting down the
backgroundOperation loop is inherently racy.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close
[
https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14076733#comment-14076733
]
ASF GitHub Bot commented on CURATOR-126:
Github user dragonsinth commented on a diff in the pull request:
https://github.com/apache/curator/pull/23#discussion_r15487030
--- Diff:
curator-framework/src/main/java/org/apache/curator/framework/imps/CuratorFrameworkImpl.java
---
@@ -74,7 +71,7 @@
private final NamespaceFacadeCache namespaceFacadeCache;
private final NamespaceWatcherMap namespaceWatcherMap = new
NamespaceWatcherMap(this);
-private volatile ExecutorService executorService;
+private volatile Thread backgroundThread;
--- End diff --
The bug is simple: Executor.shutdownNow() calls FutureTask.cancel(), which
on older JDK versions has a bug where it can interrupt the wrong thread,
causing all sorts of problems. Manually interrupting a thread does not have
this problem. Given that this Executor is only every used to run one task (the
backgroundOperationsLoop) we can simply switch to a Thread and avoid that bug.
IllegalStateException in performBackgroundOperation during close
Key: CURATOR-126
URL: https://issues.apache.org/jira/browse/CURATOR-126
Project: Apache Curator
Issue Type: Bug
Components: Framework
Affects Versions: 2.5.0
Reporter: Scott Blum
Assignee: Cameron McKenzie
Original Estimate: 24h
Remaining Estimate: 24h
{code}
[CuratorFramework-0] ERROR
org.apache.curator.framework.imps.CuratorFrameworkImpl - Background
exception was not retry-able or retry gave up
java.lang.IllegalStateException: Client is not started
at
com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at
org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:807)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:793)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.access$400(CuratorFrameworkImpl.java:57)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:275)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
{code}
I see this sometimes during test runs; I believe this happens because
CuratorZookeeperClient.started gets set to false during shutdown, but the
backgroundOperation loop can still be running since shutting down the
backgroundOperation loop is inherently racy.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close
[
https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14076743#comment-14076743
]
ASF GitHub Bot commented on CURATOR-126:
Github user Randgalt commented on a diff in the pull request:
https://github.com/apache/curator/pull/23#discussion_r15487369
--- Diff:
curator-framework/src/main/java/org/apache/curator/framework/imps/CuratorFrameworkImpl.java
---
@@ -74,7 +71,7 @@
private final NamespaceFacadeCache namespaceFacadeCache;
private final NamespaceWatcherMap namespaceWatcherMap = new
NamespaceWatcherMap(this);
-private volatile ExecutorService executorService;
+private volatile Thread backgroundThread;
--- End diff --
But doesn't that mean that Executor.shutdownNow() is broken throughout the
code? If so, I think there should be a separate issue to fix it globally.
IllegalStateException in performBackgroundOperation during close
Key: CURATOR-126
URL: https://issues.apache.org/jira/browse/CURATOR-126
Project: Apache Curator
Issue Type: Bug
Components: Framework
Affects Versions: 2.5.0
Reporter: Scott Blum
Assignee: Cameron McKenzie
Original Estimate: 24h
Remaining Estimate: 24h
{code}
[CuratorFramework-0] ERROR
org.apache.curator.framework.imps.CuratorFrameworkImpl - Background
exception was not retry-able or retry gave up
java.lang.IllegalStateException: Client is not started
at
com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at
org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:807)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:793)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.access$400(CuratorFrameworkImpl.java:57)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:275)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
{code}
I see this sometimes during test runs; I believe this happens because
CuratorZookeeperClient.started gets set to false during shutdown, but the
backgroundOperation loop can still be running since shutting down the
backgroundOperation loop is inherently racy.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close
[
https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14076839#comment-14076839
]
ASF GitHub Bot commented on CURATOR-126:
Github user dragonsinth commented on a diff in the pull request:
https://github.com/apache/curator/pull/23#discussion_r15490243
--- Diff:
curator-framework/src/main/java/org/apache/curator/framework/imps/CuratorFrameworkImpl.java
---
@@ -74,7 +71,7 @@
private final NamespaceFacadeCache namespaceFacadeCache;
private final NamespaceWatcherMap namespaceWatcherMap = new
NamespaceWatcherMap(this);
-private volatile ExecutorService executorService;
+private volatile Thread backgroundThread;
--- End diff --
Fair point, I'll revert.
BTW: I tried tracing back through the code and was not able to locate the
code path from ExecutorService.shutdownNow() - FutureTask.cancel() under 1.6.
So I might actually be confused and thinking of a Guava executor and not a JDK
one, it's possible the JDK shutdownNow() is actually safe. If so, apologizes
for the mis-info.
Either way, CloseableExecutorService.close() probably does have the issue
since it does an explicit cancel(true).
IllegalStateException in performBackgroundOperation during close
Key: CURATOR-126
URL: https://issues.apache.org/jira/browse/CURATOR-126
Project: Apache Curator
Issue Type: Bug
Components: Framework
Affects Versions: 2.5.0
Reporter: Scott Blum
Assignee: Cameron McKenzie
Original Estimate: 24h
Remaining Estimate: 24h
{code}
[CuratorFramework-0] ERROR
org.apache.curator.framework.imps.CuratorFrameworkImpl - Background
exception was not retry-able or retry gave up
java.lang.IllegalStateException: Client is not started
at
com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at
org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:807)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:793)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.access$400(CuratorFrameworkImpl.java:57)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:275)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
{code}
I see this sometimes during test runs; I believe this happens because
CuratorZookeeperClient.started gets set to false during shutdown, but the
backgroundOperation loop can still be running since shutting down the
backgroundOperation loop is inherently racy.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close
[
https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14076842#comment-14076842
]
ASF GitHub Bot commented on CURATOR-126:
Github user Randgalt commented on a diff in the pull request:
https://github.com/apache/curator/pull/23#discussion_r15490376
--- Diff:
curator-framework/src/main/java/org/apache/curator/framework/CuratorFrameworkFactory.java
---
@@ -239,6 +241,16 @@ public Builder connectionTimeoutMs(int
connectionTimeoutMs)
}
/**
+ * @param closeWaitMs time to wait during close to join background
threads
--- End diff --
Sorry to be pedantic, but this would be better named maxCloseWaitMs.
IllegalStateException in performBackgroundOperation during close
Key: CURATOR-126
URL: https://issues.apache.org/jira/browse/CURATOR-126
Project: Apache Curator
Issue Type: Bug
Components: Framework
Affects Versions: 2.5.0
Reporter: Scott Blum
Assignee: Cameron McKenzie
Original Estimate: 24h
Remaining Estimate: 24h
{code}
[CuratorFramework-0] ERROR
org.apache.curator.framework.imps.CuratorFrameworkImpl - Background
exception was not retry-able or retry gave up
java.lang.IllegalStateException: Client is not started
at
com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at
org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:807)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:793)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.access$400(CuratorFrameworkImpl.java:57)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:275)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
{code}
I see this sometimes during test runs; I believe this happens because
CuratorZookeeperClient.started gets set to false during shutdown, but the
backgroundOperation loop can still be running since shutting down the
backgroundOperation loop is inherently racy.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close
[
https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14076884#comment-14076884
]
ASF GitHub Bot commented on CURATOR-126:
Github user Randgalt commented on a diff in the pull request:
https://github.com/apache/curator/pull/23#discussion_r15491355
--- Diff:
curator-framework/src/main/java/org/apache/curator/framework/CuratorFrameworkFactory.java
---
@@ -239,6 +241,16 @@ public Builder connectionTimeoutMs(int
connectionTimeoutMs)
}
/**
+ * @param closeWaitMs time to wait during close to join background
threads
--- End diff --
I think that’s less important as it’s not visible. Up to you.
From: Scott Blum notificati...@github.com
Reply: apache/curator re...@reply.github.com
Date: July 28, 2014 at 4:13:43 PM
To: apache/curator cura...@noreply.github.com
Cc: Jordan Zimmerman jor...@jordanzimmerman.com
Subject: Re: [curator] CURATOR-126: Fix race condition in
CuratorFrameworkImpl.close() (#23)
In
curator-framework/src/main/java/org/apache/curator/framework/CuratorFrameworkFactory.java:
@@ -239,6 +241,16 @@ public Builder connectionTimeoutMs(int
connectionTimeoutMs)
}
/**
+ * @param closeWaitMs time to wait during close to join
background threads
done; what about the constant?
—
Reply to this email directly or view it on GitHub.
IllegalStateException in performBackgroundOperation during close
Key: CURATOR-126
URL: https://issues.apache.org/jira/browse/CURATOR-126
Project: Apache Curator
Issue Type: Bug
Components: Framework
Affects Versions: 2.5.0
Reporter: Scott Blum
Assignee: Cameron McKenzie
Original Estimate: 24h
Remaining Estimate: 24h
{code}
[CuratorFramework-0] ERROR
org.apache.curator.framework.imps.CuratorFrameworkImpl - Background
exception was not retry-able or retry gave up
java.lang.IllegalStateException: Client is not started
at
com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at
org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:807)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:793)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.access$400(CuratorFrameworkImpl.java:57)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:275)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
{code}
I see this sometimes during test runs; I believe this happens because
CuratorZookeeperClient.started gets set to false during shutdown, but the
backgroundOperation loop can still be running since shutting down the
backgroundOperation loop is inherently racy.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close
[
https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14076878#comment-14076878
]
ASF GitHub Bot commented on CURATOR-126:
Github user dragonsinth commented on a diff in the pull request:
https://github.com/apache/curator/pull/23#discussion_r15491274
--- Diff:
curator-framework/src/main/java/org/apache/curator/framework/CuratorFrameworkFactory.java
---
@@ -239,6 +241,16 @@ public Builder connectionTimeoutMs(int
connectionTimeoutMs)
}
/**
+ * @param closeWaitMs time to wait during close to join background
threads
--- End diff --
done; what about the constant?
IllegalStateException in performBackgroundOperation during close
Key: CURATOR-126
URL: https://issues.apache.org/jira/browse/CURATOR-126
Project: Apache Curator
Issue Type: Bug
Components: Framework
Affects Versions: 2.5.0
Reporter: Scott Blum
Assignee: Cameron McKenzie
Original Estimate: 24h
Remaining Estimate: 24h
{code}
[CuratorFramework-0] ERROR
org.apache.curator.framework.imps.CuratorFrameworkImpl - Background
exception was not retry-able or retry gave up
java.lang.IllegalStateException: Client is not started
at
com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at
org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:807)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:793)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.access$400(CuratorFrameworkImpl.java:57)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:275)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
{code}
I see this sometimes during test runs; I believe this happens because
CuratorZookeeperClient.started gets set to false during shutdown, but the
backgroundOperation loop can still be running since shutting down the
backgroundOperation loop is inherently racy.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close
[
https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14076932#comment-14076932
]
ASF GitHub Bot commented on CURATOR-126:
Github user cammckenzie commented on the pull request:
https://github.com/apache/curator/pull/23#issuecomment-50406175
Do you have a unit test to reproduce? I cooked one up which could reproduce
the issue, but I hadn't found a way for it to work with assertions. I could
only verify that the exception was being logged. I can still commit it though
if it's considered of use.
IllegalStateException in performBackgroundOperation during close
Key: CURATOR-126
URL: https://issues.apache.org/jira/browse/CURATOR-126
Project: Apache Curator
Issue Type: Bug
Components: Framework
Affects Versions: 2.5.0
Reporter: Scott Blum
Assignee: Jordan Zimmerman
Fix For: 2.7.0
Original Estimate: 24h
Remaining Estimate: 24h
{code}
[CuratorFramework-0] ERROR
org.apache.curator.framework.imps.CuratorFrameworkImpl - Background
exception was not retry-able or retry gave up
java.lang.IllegalStateException: Client is not started
at
com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at
org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:807)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:793)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.access$400(CuratorFrameworkImpl.java:57)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:275)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
{code}
I see this sometimes during test runs; I believe this happens because
CuratorZookeeperClient.started gets set to false during shutdown, but the
backgroundOperation loop can still be running since shutting down the
backgroundOperation loop is inherently racy.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close
[
https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14076966#comment-14076966
]
ASF GitHub Bot commented on CURATOR-126:
Github user dragonsinth commented on the pull request:
https://github.com/apache/curator/pull/23#issuecomment-50407804
That would be great. If you can send me a commit or diff, I'd be happy to
play with trying to test it programmatically.
IllegalStateException in performBackgroundOperation during close
Key: CURATOR-126
URL: https://issues.apache.org/jira/browse/CURATOR-126
Project: Apache Curator
Issue Type: Bug
Components: Framework
Affects Versions: 2.5.0
Reporter: Scott Blum
Assignee: Jordan Zimmerman
Fix For: 2.7.0
Original Estimate: 24h
Remaining Estimate: 24h
{code}
[CuratorFramework-0] ERROR
org.apache.curator.framework.imps.CuratorFrameworkImpl - Background
exception was not retry-able or retry gave up
java.lang.IllegalStateException: Client is not started
at
com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at
org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:807)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:793)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.access$400(CuratorFrameworkImpl.java:57)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:275)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
{code}
I see this sometimes during test runs; I believe this happens because
CuratorZookeeperClient.started gets set to false during shutdown, but the
backgroundOperation loop can still be running since shutting down the
backgroundOperation loop is inherently racy.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close
[
https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14077122#comment-14077122
]
ASF GitHub Bot commented on CURATOR-126:
Github user cammckenzie commented on the pull request:
https://github.com/apache/curator/pull/23#issuecomment-50416483
I have pushed a unit test up onto the CURATOR-126 branch. Have a play with
it, I still seem to be getting the error logged when running against the fix.
Could be something bogus in the test though.
IllegalStateException in performBackgroundOperation during close
Key: CURATOR-126
URL: https://issues.apache.org/jira/browse/CURATOR-126
Project: Apache Curator
Issue Type: Bug
Components: Framework
Affects Versions: 2.5.0
Reporter: Scott Blum
Assignee: Jordan Zimmerman
Fix For: 2.7.0
Original Estimate: 24h
Remaining Estimate: 24h
{code}
[CuratorFramework-0] ERROR
org.apache.curator.framework.imps.CuratorFrameworkImpl - Background
exception was not retry-able or retry gave up
java.lang.IllegalStateException: Client is not started
at
com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at
org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:807)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:793)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.access$400(CuratorFrameworkImpl.java:57)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:275)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
{code}
I see this sometimes during test runs; I believe this happens because
CuratorZookeeperClient.started gets set to false during shutdown, but the
backgroundOperation loop can still be running since shutting down the
backgroundOperation loop is inherently racy.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close
[
https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14077164#comment-14077164
]
ASF GitHub Bot commented on CURATOR-126:
Github user Randgalt commented on the pull request:
https://github.com/apache/curator/pull/23#issuecomment-50418758
I pushed an update to the test that has an assert. I tested it with the old
background thread code and the test fails. It succeeds with the new code.
-JZ
From: cammckenzie notificati...@github.com
Reply: apache/curator re...@reply.github.com
Date: July 28, 2014 at 6:29:46 PM
To: apache/curator cura...@noreply.github.com
Cc: Jordan Zimmerman jor...@jordanzimmerman.com
Subject: Re: [curator] CURATOR-126: Fix race condition in
CuratorFrameworkImpl.close() (#23)
I have pushed a unit test up onto the CURATOR-126 branch. Have a play with
it, I still seem to be getting the error logged when running against the fix.
Could be something bogus in the test though.
—
Reply to this email directly or view it on GitHub.
IllegalStateException in performBackgroundOperation during close
Key: CURATOR-126
URL: https://issues.apache.org/jira/browse/CURATOR-126
Project: Apache Curator
Issue Type: Bug
Components: Framework
Affects Versions: 2.5.0
Reporter: Scott Blum
Assignee: Jordan Zimmerman
Fix For: 2.7.0
Original Estimate: 24h
Remaining Estimate: 24h
{code}
[CuratorFramework-0] ERROR
org.apache.curator.framework.imps.CuratorFrameworkImpl - Background
exception was not retry-able or retry gave up
java.lang.IllegalStateException: Client is not started
at
com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at
org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:807)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:793)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.access$400(CuratorFrameworkImpl.java:57)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:275)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
{code}
I see this sometimes during test runs; I believe this happens because
CuratorZookeeperClient.started gets set to false during shutdown, but the
backgroundOperation loop can still be running since shutting down the
backgroundOperation loop is inherently racy.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close
[
https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14077168#comment-14077168
]
ASF GitHub Bot commented on CURATOR-126:
Github user Randgalt commented on the pull request:
https://github.com/apache/curator/pull/23#issuecomment-50419120
Sorry Scott - it looks like CURATOR-126 hasn’t sync’d yet to the Github
repo. The whole Github sync think is a lot of black magic. It is, however,
here:
https://git-wip-us.apache.org/repos/asf?p=curator.git;a=tree;h=refs/heads/CURATOR-126;hb=CURATOR-126
From: Scott Blum notificati...@github.com
Reply: apache/curator re...@reply.github.com
Date: July 28, 2014 at 7:03:46 PM
To: apache/curator cura...@noreply.github.com
Cc: Jordan Zimmerman jor...@jordanzimmerman.com
Subject: Re: [curator] CURATOR-126: Fix race condition in
CuratorFrameworkImpl.close() (#23)
Where are the commits? I did a git remote update on both my fork and apache
and couldn't find them.
—
Reply to this email directly or view it on GitHub.
IllegalStateException in performBackgroundOperation during close
Key: CURATOR-126
URL: https://issues.apache.org/jira/browse/CURATOR-126
Project: Apache Curator
Issue Type: Bug
Components: Framework
Affects Versions: 2.5.0
Reporter: Scott Blum
Assignee: Jordan Zimmerman
Fix For: 2.7.0
Original Estimate: 24h
Remaining Estimate: 24h
{code}
[CuratorFramework-0] ERROR
org.apache.curator.framework.imps.CuratorFrameworkImpl - Background
exception was not retry-able or retry gave up
java.lang.IllegalStateException: Client is not started
at
com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at
org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:807)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:793)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.access$400(CuratorFrameworkImpl.java:57)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:275)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
{code}
I see this sometimes during test runs; I believe this happens because
CuratorZookeeperClient.started gets set to false during shutdown, but the
backgroundOperation loop can still be running since shutting down the
backgroundOperation loop is inherently racy.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
