Hi, Thank you Pat for the reply.
I have noticed couple of issues, while building HA using the 'election-recipe'. It would be helpful to shape the 'election-recipe' algo by considering these use cases. I would be thankful if the author/community members can have a look on these cases and the patches/solutions. Thanks, Rakesh ________________________________________ From: Patrick Hunt [[email protected]] Sent: Wednesday, November 30, 2011 2:54 AM To: [email protected] Subject: Re: LES-Recipe patches >We've been pretty swamped with getting out 3.3.4 and 3.4.0. Now those >are out we're in better shape. However it would be great if community >members could review and comment on the patches. (any patch in PA >would be great) Patrick On Tue, Nov 29, 2011 at 4:17 AM, Rakesh R <[email protected]> wrote: > Hi, > > > > > > I've accumulated a bunch of patches that should (hopefully) improve > les-recipe usage and need review and inclusion. Please be so kind and give > them a look: > > > > ZOOKEEPER-1209 : LeaderElection recipe doesn't handle the split-brain issue, > n/w disconnection can bring both the client nodes to be in ELECTED > > > > ZOOKEEPER-1219 : LeaderElectionSupport recipe is unnecessarily dispatching > the READY_START event even if the ELECTED node stopped/expired simultaneously. > > > > ZOOKEEPER-1225 : Successive invocation of LeaderElectionSupport.start() will > bring the ELECTED node to READY and cause no one in ELECTED state. > > > > Thank you, > Rakesh R
