curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jordan Zimmerman (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CURATOR-123) ConnectionStateListener advertises READ_ONLY instead of CONNECTED the first time around
Date Wed, 23 Jul 2014 17:05:39 GMT

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

Jordan Zimmerman edited comment on CURATOR-123 at 7/23/14 5:04 PM:
-------------------------------------------------------------------

If you still think there is a Curator issue, please open a new issue. I'm going to fix this
one up.


was (Author: randgalt):
If you still think there is a Curator, please open a new issue. I'm going to fix this one
up.

> ConnectionStateListener advertises READ_ONLY instead of CONNECTED the first time around
> ---------------------------------------------------------------------------------------
>
>                 Key: CURATOR-123
>                 URL: https://issues.apache.org/jira/browse/CURATOR-123
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Client, Framework
>    Affects Versions: 2.6.0
>         Environment: Ubuntu 12.04 
> 3 ZK with readonlymode.enabled
>            Reporter: Benjamin Jaton
>            Assignee: Jordan Zimmerman
>              Labels: connection, listener
>             Fix For: 2.6.1
>
>         Attachments: Test.java
>
>
> see Test.java attached.
> When there is only 1 out of 3 zookeeper started, the initial state of the listener is
CONNECTED but should be READ_ONLY.
> NOTE: this issue got confused with CURATOR-122 and is being reworded to match CURATOR-122.



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

Mime
View raw message