curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Evaristo (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-72) Background operations don't wait for connection timeout
Date Thu, 14 Nov 2013 22:27:22 GMT

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

Evaristo commented on CURATOR-72:
---------------------------------

You can see sequences like CONNECTED , LOST , SUSPENDED now with Curator 2.3.0

I think that problem is related with the patch introduced with CURATOR-52

If before setting the SUSPENDED event you are getting a ConnectionLoss Exception (e.g. background
operation), the LOST event is fired. It is a race condition between exceptions an Zokkeper
client events, and CURATOR-52 patch is over reacting introducing LOST events and breaking
the listeners orderings.

The previous listeners sequence is not happening with Curator 2.2.0 or 2.1.0

> 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.3.1
>
>         Attachments: TestListener.java, TestListenerConnectedAtStart.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#6144)

Mime
View raw message