[
https://issues.apache.org/jira/browse/ZOOKEEPER-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16566504#comment-16566504
]
Tamas Penzes edited comment on ZOOKEEPER-3108 at 8/2/18 9:19 AM:
-----------------------------------------------------------------
I mostly find it good to separate application level configuration (in this case
configs in zoo.cfg) from instance level configuration like myid file.
Of course if you use an orchestration tool like Ansible, Chef, etc. or a
configuration management (provisioning, managing, monitoring) tool like
Cloudera Manager or Apache Ambari and you automatically regenerate your configs
it might not look important, but it still doesn't hurt.
In case we create the files by hand it should not be a problem either, since
most of the ZK clusters only consist 3 or 5 servers...
was (Author: tamaas):
I mostly find it good to separate application level configuration (in this case
configs in zoo.cfg) from instance level configuration like myid file.
Of course if you use an orchestration tool like Ansible, Chef, etc. or a
configuration management (provisioning, managing, monitoring) tool like
Cloudera Manager or Apache Ambari and you automatically regenerate your configs
it might not look important, but it still doesn't hurt.
> 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)
