zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Camille Fournier <cami...@apache.org>
Subject Re: Peer that can't become leader
Date Thu, 05 Sep 2013 16:52:51 GMT
Hi Ben,

Sorry I haven't replied to your post comment. This was "manual" in that we
made sure things like restart scripts would restart this instance last, and
we would monitor that server and restart it if it ever became the elected
leader. It's not ideal but it works, and that's the only way to do what I
suggested because observers are not voting members and thus can't help with
the datacenter failure issue.


On Thu, Sep 5, 2013 at 3:00 AM, Flavio Junqueira <fpjunqueira@yahoo.com>wrote:

> Are you asking about observers? Observers don't vote and are not elected.
> -Flavio
> -----Original Message-----
> From: "Ben Horowitz" <bhorowit@gmail.com>
> Sent: 05/09/2013 06:57
> To: "user@zookeeper.apache.org" <user@zookeeper.apache.org>
> Subject: Peer that can't become leader
> Hi all,
> Camille Fournier in her blog post on a global service discovery
> infrastructure using ZK [1] describes a setup in which, by design, a
> distinguished peer P never becomes leader.
> Is there any way of accomplishing this setup with ZK config files? Or
> would one have to watch the ensemble and restart P if ever P becomes
> leader?
> [1]
> http://whilefalse.blogspot.com/2012/12/building-global-highly-available.html#comment-form
> Thanks,
> Ben

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message