Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@zookeeper.apache.org
Received-SPF: pass (athena.apache.org: domain of hartmut.lang@googlemail.com
 designates 209.85.161.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CB54B92C.14174%jzimmerman@netflix.com>
References: 
 <CABE49h62U9P8UL0GZPjbOGA=ekpgMKJGezdoegm-4f7Y0bbGzw@mail.gmail.com>
	<CB54B92C.14174%jzimmerman@netflix.com>
Date: Mon, 6 Feb 2012 18:28:10 +0100
Message-ID: 
 <CABE49h6SXfOXRL0LKVFsmPQxbbq_vUR0pkV6rRPPC8VRnUSuTA@mail.gmail.com>
Subject: Re: curator leader reconnect
From: Hartmut Lang <hartmut.lang@googlemail.com>
To: user@zookeeper.apache.org
Content-Type: multipart/alternative; boundary=e89a8f3ba0e38dbcc204b84efc7d

--e89a8f3ba0e38dbcc204b84efc7d
Content-Type: text/plain; charset=ISO-8859-1

Hi Jordan,

thanks for your infos.
What i see in my LeaderSelector example is this:
when i just call the start() method after RECONNECT, the takeLeadership()
method is called again.
But no ephemeral node does exist in the ZK-Cluster for my client. So this
seems not to be right.
What could i do wrong?

/Hartmut
Am 6. Februar 2012 07:55 schrieb Jordan Zimmerman <jzimmerman@netflix.com>:

> 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" <hartmut.lang@googlemail.com> 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
> ><jzimmerman@netflix.com>:
> >
> >> 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" <hartmut.lang@googlemail.com> 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
> >>
> >>
>
>

--e89a8f3ba0e38dbcc204b84efc7d--