You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Flavio Junqueira (Assigned) (JIRA)" <ji...@apache.org> on 2012/04/19 20:00:40 UTC
[jira] [Assigned] (ZOOKEEPER-1411) Consolidate membership
management, distinguish between static and dynamic configuration parameters
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flavio Junqueira reassigned ZOOKEEPER-1411:
-------------------------------------------
Assignee: Alexander Shraer (was: Tadeusz Andrzej Kadłubowski)
Sorry, I didn't do it right. Fixing the assignee.
> Consolidate membership management, distinguish between static and dynamic configuration parameters
> --------------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-1411
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1411
> Project: ZooKeeper
> Issue Type: Sub-task
> Components: server
> Reporter: Alexander Shraer
> Assignee: Alexander Shraer
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1411-ver1.patch, ZOOKEEPER-1411-ver10.patch, ZOOKEEPER-1411-ver2.patch, ZOOKEEPER-1411-ver3.patch, ZOOKEEPER-1411-ver4.patch, ZOOKEEPER-1411-ver5.patch, ZOOKEEPER-1411-ver6.patch, ZOOKEEPER-1411-ver7.patch, ZOOKEEPER-1411-ver8.patch, ZOOKEEPER-1411-ver9.patch
>
>
> Currently every server has a different static configuration file. This patch distinguishes between dynamic parameters, which are now in a separate "dynamic configuration file", and static parameters which are in the usual file. The config file points to the dynamic config file by specifying "dynamicConfigFile=...". In the first stage (this patch), all cluster membership definitions are in the dynamic config file, but in the future additional parameters may be moved to the dynamic file.
> Backward compatibility makes sure that you can still use a single config file if you'd like. Only when the config is changed (once ZK-107 is in) a dynamic file is automatically created and the necessary parameters are moved to it.
> This patch also moves all membership parsing and management into the QuorumVerifier classes, and removes QuorumPeer.quorumPeers.
> The cluster membership is contained in QuorumPeer.quorumVerifier. QuorumVerifier was expanded and now has methods such as getAllMembers(), getVotingMembers(), getObservingMembers().
--
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