[
https://issues.apache.org/jira/browse/ZOOKEEPER-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16615566#comment-16615566
]
Benjamin Reed commented on ZOOKEEPER-3108:
------------------------------------------
the reason we kept myid out of the config is so that all the servers can use
the same configuration file. the id would then be tied with the data.
the id of the server should be a rather permanent thing. for example, if you
have an ensemble that has ids host1=1, host2=2, host3=3 and an observer with id
of host4=4, today to make host3 an observer and host4 a participant you have to
go through reconfiguration. with this id configuration option it is tempting to
just change the ids (host4=3 and host3=4). this can result in data loss or
corruption.
it's not a show stopper, but we do need to document it properly: even though
the id can be set via the configuration file, it should be considered bound to
the data directory.
> use a new property server.id in the zoo.cfg to substitute for myid file
> -----------------------------------------------------------------------
>
> Key: ZOOKEEPER-3108
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3108
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.5.0
> Reporter: maoling
> Assignee: maoling
> Priority: Major
> Labels: pull-request-available
> Time Spent: 50m
> Remaining Estimate: 0h
>
> When use zk in distributional model,we need to touch a myid file in
> dataDir.then write a unique number to it.It is inconvenient and not
> user-friendly,Look at an example from other distribution system such as
> kafka:it just uses broker.id=0 in the server.properties to indentify a unique
> server node.This issue is going to abandon the myid file and use a new
> property such as server.id=0 in the zoo.cfg. this fix will be applied to
> master branch,branch-3.5+,
> keep branch-3.4 unchaged.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
