You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Fangmin Lv (JIRA)" <ji...@apache.org> on 2018/08/01 04:48:00 UTC
[jira] [Commented] (ZOOKEEPER-3108) deprecated myid file and use a
new property "server.id" in the zoo.cfg
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564725#comment-16564725 ]
Fangmin Lv commented on ZOOKEEPER-3108:
---------------------------------------
I think this is a good idea, but it's better to keep backward compatible to make sure it won't break the existing users.
> 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)