You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@zookeeper.apache.org by Jack Luo <ja...@gmail.com> on 2012/07/31 19:51:34 UTC

Question about SyncConnected notification when server failover

Hi All,



During the test of sever failover with zookeeper 3.3.5, I have following
interesting findings.



1)      If the follower sever is shut down, only the clients connecting to
this failed server get SyncConnected notification.

2)      If the leader server is shut down, all clients (doesn't matter if
they connect to follower or leader servers.) get the SyncConnected
notification.



>From my current understanding, if leader server fails, only the clients
connecting to it will connect to a new server and receive the SyncConnected
notification. Look like my understanding is wrong.



Can anyone tell me that my findings are expected behaviors? Or is there any
tricky setting in server’s configuration to solve this issue?



Many thanks!



Jack

Re: Question about SyncConnected notification when server failover

Posted by Patrick Hunt <ph...@apache.org>.
When the leader fails a new leader must be elected. Until that time
all servers stop serving (they close any client connections)

Patrick

On Tue, Jul 31, 2012 at 10:51 AM, Jack Luo <ja...@gmail.com> wrote:
> Hi All,
>
>
>
> During the test of sever failover with zookeeper 3.3.5, I have following
> interesting findings.
>
>
>
> 1)      If the follower sever is shut down, only the clients connecting to
> this failed server get SyncConnected notification.
>
> 2)      If the leader server is shut down, all clients (doesn't matter if
> they connect to follower or leader servers.) get the SyncConnected
> notification.
>
>
>
> From my current understanding, if leader server fails, only the clients
> connecting to it will connect to a new server and receive the SyncConnected
> notification. Look like my understanding is wrong.
>
>
>
> Can anyone tell me that my findings are expected behaviors? Or is there any
> tricky setting in server’s configuration to solve this issue?
>
>
>
> Many thanks!
>
>
>
> Jack