curator-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benjamin Jaton <bja...@radiantlogic.com>
Subject Curator connection states
Date Tue, 15 Jul 2014 21:08:36 GMT
Hello,

When I have a 3 nodes ZooKeeper ensemble with 2 down and my read-only flag
is set on the curator client, here is what I see:

// initial connection:
ZOOKEEPER state change: CONNECTEDREADONLY
CURATOR state change: CONNECTED

// a second node comes up
ZOOKEEPER state change: CONNECTED
CURATOR state change: SUSPENDED
CURATOR state change: RECONNECTED

// that second node goes down again
ZOOKEEPER state change: CONNECTEDREADONLY
CURATOR state change: SUSPENDED
CURATOR state change: READ_ONLY

1) Shouldn't we have a READ_ONLY state initially? How can I know if the
connection is read only?
2) Why do we have the SUSPENDED states in between?

Thanks

Mime
View raw message