I think it would be good to have a design document, just to reason about it and make sure that the mechanism we are introducing is not flawed. It is easy to get these things wrong.


On Feb 18, 2010, at 11:30 PM, Henry Robinson wrote:

Hari -

It's very difficult to say how long this would take. There are a number of issues that need to be resolved by design rather than code. For example, the
question of finding the cluster when the membership has changed is

The changes to the core protocol will need substantial peer review and
testing. Judging by my experience with the observers patch, which I think is
comparable in size but probably less complex, I would expect about 3-6
months from the time someone picks up the work.


On 18 February 2010 12:28, Hariharan Subramanian <hurryha...@gmail.com>wrote:

Thanks to all of you that responded. This feature is also important to the project I am working on. Although we would have to find someone with the
right skills to contribute to it.

Henry, Do you have an estimate on how long this task would take if someone
were to start with your prototype?

Thanks again
~ Hari

On Thu, Feb 18, 2010 at 1:35 PM, Henry Robinson <he...@cloudera.com>wrote:

Hi -

Yes, I'm still interested in this JIRA but it's a significant change to ZK which would be best suited for probably the 4.0 release. I have a rough implementation that 'works' but still leaves some issues unresolved. I
have a great deal of time for this issue at the moment though, which is
it's stalled a bit - other ZK issues are more pressing. This would be a really great project for anyone looking for a meaty distributed systems project; I'm happy to offer guidance and advice if anyone wants to take it


On 18 February 2010 09:58, Patrick Hunt <ph...@apache.org> wrote:

There are ways to "dynamically" update the cluster membership today, granted while they are dynamic they are not dynamic in the sense of 107:
http://bit.ly/bTTdDK (see item 6)

107 is still pending. Henry was interested to implement this, I'm not
his current status. Henry? I think this is a good feature to add, but it brings up a number of issues that we need to work through. Given that
ppl rarely change cluster membership, and the fact that there are
available today, there hasn't been a lot of demand for this.


Hariharan Subramanian wrote:

Dear Zookeeper community,

I would like to know the status of issue ZOOKEEPER-107 (Allow dynamic
changes to server cluster membership) which is assigned to Henry

Is this the right forum to ask this question or should I post an update
the bug report?

-- Hari

Henry Robinson
Software Engineer

--… …--
.... .- .-. ..

Henry Robinson
Software Engineer

Reply via email to