[
https://issues.apache.org/jira/browse/ZOOKEEPER-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Shraer updated ZOOKEEPER-107:
---------------------------------------
Attachment: ZOOKEEPER-107-1-Mar.patch
not for inclusion.
- added backward compatibility mode for configuration files: the feature
generally requires that the config file points to a separate membership file
(where the server, group and weight definitions are supposed to be), but will
now also work with a standard single config file. In that case, if a
reconfiguration happens, we create a membership file and edit the config file
to point to the new membership file. Otherwise the config file remains
unchanged.
- Fixed small problem in C client
> 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: Alexander Shraer
> Fix For: 3.5.0
>
> Attachments: SimpleAddition.rtf, ZOOKEEPER-107-1-Mar.patch,
> ZOOKEEPER-107-28-Feb.patch, ZOOKEEPER-107-28-Feb.patch,
> ZOOKEEPER-107-29-Feb.patch, zoo_replicated1.cfg, zoo_replicated1.members,
> zookeeper-3.4.0.jar, zookeeper-dev-fatjar.jar,
> zookeeper-reconfig-sep11.patch, zookeeper-reconfig-sep12.patch
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
