zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Nixon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-3108) deprecated myid file and use a new property "server.id" in the zoo.cfg
Date Wed, 01 Aug 2018 18:54:00 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16565814#comment-16565814
] 

Brian Nixon commented on ZOOKEEPER-3108:
----------------------------------------

This seems like a good idea to me (provided myid files are still supported) to give admins
a bit more flexibility.

One reason I can think of to keep using a separate myid file is that the server id is the
one property guaranteed to be unique for a given peer across the ensemble. All other properties
and jvm flags may be identical across every instance. This makes reasoning about configuration
files very easy - one simply propagates the same file everywhere and no custom logic is needed
when comparing them.

Here's a link to an old discussion around myid -> http://zookeeper-user.578899.n2.nabble.com/The-idea-behind-myid-td3711269.html

>  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)

Mime
View raw message