Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Zookeeper >> mail # user >> curator leader reconnect


Copy link to this message
-
Re: curator leader reconnect
No - don't call close. I'm afraid that it's a bit confusing. It was an
afterthought. Maybe I should add a restart() method or something.

-JZ

On 2/5/12 10:48 PM, "Hartmut Lang" <[EMAIL PROTECTED]> wrote:

>Thanks for your answer.
>If i call start() again on the same instance, should i call close()
>before?
>
>My first attempt was to call close() on the LeaderSelector on a
>LOST-Event.
>Well then of course i do not get again the RECONNECT event on the
>LeaderSelectorListener.
>
>/Hartmut
>
>Am 5. Februar 2012 23:53 schrieb Jordan Zimmerman
><[EMAIL PROTECTED]>:
>
>> You can either create a new LeaderSelector or call start() again on your
>> existing leader instance. Whatever's easier for your use-case.
>>
>> -Jordan
>>
>> On 2/5/12 8:09 AM, "Hartmut Lang" <[EMAIL PROTECTED]> wrote:
>>
>> >Hi,
>> >
>> >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
>> >RECONNECTED occurs?
>> >How can the LeaderSelector be restarted on RECONNECTED?
>> >
>> >Hope someone can help,
>> >Hartmut
>>
>>
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB