[ZOOKEEPER-1411] Consolidate membership management, distinguish between static and dynamic configuration parameters

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.5.0
• Component/s: server
• Hadoop Flags: Reviewed
• Assignee: Alexander Shraer
• Reporter: Alexander Shraer
• Created: 09/Mar/12 01:02
• Updated: 02/May/13 02:30
• Resolved: 02/Apr/13 06:33

Description

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().

Issue Links

• breaks: ZOOKEEPER-1540 ZOOKEEPER-1411 breaks backwards compatibility
• breaks: ZOOKEEPER-1625 zkServer.sh is looking for clientPort in config file, but it may no longer be there with ZK-1411
• is depended upon by: ZOOKEEPER-1660 Add documentation for dynamic reconfiguration
• is depended upon by: ZOOKEEPER-107 Allow dynamic changes to server cluster membership