Patrick Hunt commented on ZOOKEEPER-107:

I've only been following this a bit, and I see bits/pieces in the comments but 
not sure I follow it all -- some questions around the plan wrt manageability:

1) adding removing servers, server itself needs to be configured, any changes 
needed to config on existing ensemble? I see Raghu has similar comment on this
2) JMX - what's the plan? what additional properties/actions will be supported?
3) 4letter words - same issues as jmx
4) debug-ability - ensure adequate logging (log4j) on ensemble

5) security - will an ensemble allow any server to connect to it? today we have 
ensemble participants hardwired into the config of each of the servers right?

testing and b/w compat -- are we ensuring b/w compat btw this version and 
previous versions? (I'm probably going to look at beefing up unit & systest 
next, esp around b/w compat, so would be good to have a better idea where this 
is headed). IMO this patch must include unit as well as systest before it is 

documentation will be needed as well.

Perhaps a wiki "proposal" page should be created that will capture the "current 
proposal" for easy review of this feature? This JIRA can capture ongoing 
discussion, with agreed upon results capture in the wiki design/functional 
document. I know it would help me alot.

> Allow dynamic changes to server cluster membership
> --------------------------------------------------
>                 Key: ZOOKEEPER-107
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-107
>             Project: Zookeeper
>          Issue Type: Improvement
>          Components: server
>            Reporter: Patrick Hunt
>            Assignee: Henry Robinson
>         Attachments: SimpleAddition.rtf
> Currently cluster membership is statically defined, adding/removing hosts 
> to/from the server cluster dynamically needs to be supported.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to