[
https://issues.apache.org/jira/browse/ZOOKEEPER-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16596205#comment-16596205
]
maoling commented on ZOOKEEPER-3108:
------------------------------------
[~hanm]
IMO, put the myid in the *dataDir* is not very good .if I want to rm -rf the
data in this directory,I will delete the myid file by mistake.At least,we
should move myid into *conf*?
For upgrade and solve the compatibility, we can firstly read the *server.id*
from *zoo.cfg*.
if find a number,return this number
if find nothing,then we read from myid file in the *dataDir* if the version is
old.
> deprecated myid file and use a new property "server.id" in the zoo.cfg
> -----------------------------------------------------------------------
>
> 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
>
> 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)
