[
https://issues.apache.org/jira/browse/ZOOKEEPER-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16595906#comment-16595906
]
Michael Han commented on ZOOKEEPER-3108:
----------------------------------------
I think we can provide an option to move unique identifier of the server from
myid file to zoo.cfg - thus avoiding creating myid file, but I don't feel this
approach is much more convenient comparing to the current approach of putting
the server id in myid file - the unique id still has to be created for each
server it's just put into a different place. [~maoling] comments?
As others also mentioned, regardless of what additional options we are going to
add, please keep the current myid approach. It would be a pain for those who
operates ZK to upgrade if we just abandon the myid file completely.
> 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)
