[
https://issues.apache.org/jira/browse/ZOOKEEPER-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225763#comment-13225763
]
Alexander Shraer commented on ZOOKEEPER-1411:
---------------------------------------------
The patch creates the option to have a config file and a separate membership
file.
-----------
Example of config file:
tickTime=2000
dataDir=/home/shralex/zookeeper-3.3.2/zookeeper1
initLimit=5
syncLimit=2
membershipFile=/home/shralex/zookeeper-3.3.2/conf/zoo_replicated1.members
Example of membership file:
server.1=localhost:2780:2783:participant;localhost:2791
server.2=localhost:2781:2784;2792
server.3=localhost:2782:2785:participant;2793
-------------
the cfg file points to the membership file by specifying "membershipFile". The
membership file has all information about membership and ports. You must
specify all client ports in that file - this info is separated by ";" from the
usual server info. The cfg file can still include client ports (or hostname and
port, but if given they must be the same as in the membership file.
Backward compatibility: you can still use one configuration file and that would
work fine. But, if the configuration changes (will only happen once ZK-107 is
in), the config file is automatically split to two files, and the files are
updated accordingly.
> Consolidate membership management and add client port information
> -----------------------------------------------------------------
>
> Key: ZOOKEEPER-1411
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1411
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
> Reporter: Alexander Shraer
> Assignee: Alexander Shraer
> Fix For: 3.5.0
>
>
> Currently every server has a different configuration file. With this patch,
> we will have all cluster membership definitions in a single file, and every
> sever can have a copy of this file.
> This also solves ZOOKEEPER-1113
--
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
