zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jordan Zimmerman <jzimmer...@netflix.com>
Subject Re: curator leader reconnect
Date Sun, 05 Feb 2012 22:53:43 GMT
You can either create a new LeaderSelector or call start() again on your
existing leader instance. Whatever's easier for your use-case.


On 2/5/12 8:09 AM, "Hartmut Lang" <hartmut.lang@googlemail.com> wrote:

>i work on a small demo application using the Curator Leader-Election.
>What i understand from the wiki is that on a connection LOST-event, the
>leader should end his takeLeadership method.
>But what should be done with the LeaderSelector instance?
>Should this be also closed on a LOST-event? Or can it be re-used, when
>How can the LeaderSelector be restarted on RECONNECTED?
>Hope someone can help,

View raw message