[
https://issues.apache.org/jira/browse/CURATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13869121#comment-13869121
]
Jordan Zimmerman commented on CURATOR-72:
-----------------------------------------
I see the issue. As [~barkbay] points out, there's a race. When Curator goes to
SUSPENDED, it starts a background sync() call to check if it needs to go to
LOST. During this, Curator might reset the connection. The new reset connection
will succeed, but the previous connection fails. What needs to happen is
Curator needs to make note that the connection got reset and ignore the
background sync() failure which is now for a no longer used ZooKeeper instance.
> Background operations don't wait for connection timeout
> -------------------------------------------------------
>
> Key: CURATOR-72
> URL: https://issues.apache.org/jira/browse/CURATOR-72
> Project: Apache Curator
> Issue Type: Bug
> Components: Framework
> Affects Versions: 2.3.0
> Reporter: Evaristo Camarero
> Assignee: Jordan Zimmerman
> Fix For: 2.4.0
>
> Attachments: TestListener.java, TestListenerConnectedAtStart.java,
> TestListenerSequence.java, TestListenerWithLeaderSelector.java, test.java
>
>
> Background operations don't wait for the configured connection timeout before
> failing. Attached test shows the problem.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
