You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@curator.apache.org by "Jordan Zimmerman (JIRA)" <ji...@apache.org> on 2014/07/23 00:50:38 UTC

[jira] [Resolved] (CURATOR-122) ConnectionStateListener advertises READ_ONLY instead of CONNECTED the first time around

     [ https://issues.apache.org/jira/browse/CURATOR-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jordan Zimmerman resolved CURATOR-122.
--------------------------------------

    Resolution: Duplicate

I think I screwed up the issues. Anyway, READ_ONLY should be fixed. Please verify.

> ConnectionStateListener advertises READ_ONLY instead of CONNECTED the first time around
> ---------------------------------------------------------------------------------------
>
>                 Key: CURATOR-122
>                 URL: https://issues.apache.org/jira/browse/CURATOR-122
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Client
>    Affects Versions: 2.6.0
>         Environment: Ubuntu 12.04
> 3 ZK with readonlymode.enabled
>            Reporter: Benjamin Jaton
>            Priority: Critical
>              Labels: connection, listener
>
> When there is only 1 out of 3 zookeeper started, the initial state of the listener is CONNECTED but should be READ_ONLY.



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