curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Jaton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-122) ConnectionStateListener advertises READ_ONLY instead of CONNECTED the first time around
Date Tue, 22 Jul 2014 22:40:38 GMT

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

Benjamin Jaton commented on CURATOR-122:
----------------------------------------

CURATOR-122 is about the very first state, CURATOR-123 is about the ConnectionStateManager
sending duplicate events for when the ensemble goes read only.

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

Mime
View raw message