A good place to put this code is in a pre-connect callback (which is added before calling connect). This callback will be invoked after there is an active connection to ZK, but before you are registered with the cluster (e.g. creating a live instance node as a participant, or trying to become the leader as a controller).
Kanak ________________________________ > Date: Sun, 16 Feb 2014 01:06:12 -0800 > Subject: Re: Helix 0.6.2: HelixManager start > From: [email protected] > To: [email protected] > > I believe you need to be connect first. Technically some listeners can > be added without connecting but we in favour of symmetry we enforced > invoking connect method before adding new listeners. > > > On Sun, Feb 16, 2014 at 12:29 AM, Sandeep Nayak > <[email protected]<mailto:[email protected]>> wrote: > Should the listeners be registered before invoking connect? Does the > order matter? > > > On Sat, Feb 15, 2014 at 10:12 PM, Kanak Biscuitwala > <[email protected]<mailto:[email protected]>> wrote: > That's a bug in the javadoc. Yes, connect completely encapsulates > everything necessary. > > Kanak > ________________________________ >> Date: Sat, 15 Feb 2014 22:09:39 -0800 >> Subject: Helix 0.6.2: HelixManager start >> From: [email protected]<mailto:[email protected]> >> To: [email protected]<mailto:[email protected]> >> >> The >> javadocs > http://helix.apache.org/javadocs/0.6.2-incubating/reference/org/apache/helix/HelixManager.html > >> state that after connect I should invoke start on the helix manager >> instance. >> >> However, I dont see the start API on the HelixManager, does the connect >> do the start part too? >> >> Thanks, >> >> Sandeep > >
