Flavio, Ted, Henry, Scott, this would perfectly well for my use case
provided:
SINGLE ENSEMBLE:
GROUP A : ZK Servers w/ read/write AND Leader Elections
GROUP B : ZK Servers w/ read/write W/O Leader Elections
So, we can craft this via Observers and Hiererarchial Quorum groups?
Both of the options that Scott mentioned are quite interesting. Quite a few
of our users are interested in these two features. I think for 2, we should
be able to use observers with a subscription to the master cluster with
interested in a special subtree. That avoids too much of cross talk.
Henry, cool. When youre patch is ready for testing, I'll devote some
time to take a test pass on it.
-Original Message-
From: Henry Robinson [mailto:he...@cloudera.com]
Sent: Monday, July 20, 2009 2:54 PM
To: zookeeper-user@hadoop.apache.org
Subject: Re: Leader Elections
On Mon, Jul 20,
For the partial subscription, my take right now is that it should be
part of the registration procedure. When an observer joins, it
contacts some ensemble server (a follower or the current leader) and
appends a path to the initial message it sends to this server. This
path corresponds to
