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 Wed, 08 Jan 2014 11:44:52 GMT

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

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

I have run the regression of my app, and I think there is an issue with the patch

I describe the use case:
1.- CuratorFramework connected to healthy ZK ensemble with several recipes related (leader
election, nodeCache, pathchildrencache)
2.- Stop all ZK server from the ensemble
3.- CuratorFramework triggers SUSPENDED (As expected)
4.- CuratorFramework triggers LOST (As expected)
5.- Starting all ZK servers from the ensemble again
7.- CuratorFramework triggers RECONNECTED (As expected)
8.- After step 7, CuratorFramework triggers LOST (NOT EXPECTED)

I will try to provide a test that shows the issue asap

> 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,
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)

Mime
View raw message