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

some one commented on ZOOKEEPER-2031:
-------------------------------------

Wanted to clarify this:

> The tag has to be assigned at the bootup of the server. The idea is that if 
> you reconfig and you want to add server 2, but don't specify the right tag 
> that server 2 has upon bootup, server 2 won't be added.

There are two scenarios:
a) server2 with tagA exists, and you try to reconfig add server2 with tagB into 
cluster 1, but server2 with tagB doesn't exist, nothing will be added, because 
that server just doesn't exist. This relates to my answer to question (2) 
above, which talks about how the tag is part of the server's identity.

b) server2 with tagA exists and server2 with tagB exists, you try to reconfig 
add server2 with tagB into cluster1, server2 with tagB gets added instead of 
server2 tagA, because that's what the user requested.

> Support tagging a QuorumServer
> ------------------------------
>
>                 Key: ZOOKEEPER-2031
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2031
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: server
>            Reporter: some one
>            Assignee: some one
>             Fix For: 3.5.1, 3.6.0
>
>         Attachments: ZOOKEEPER-2031-Additional.patch, ZOOKEEPER-2031.patch
>
>
> Currently ZooKeeper only allows using the server id which is an integer for 
> identifying servers. For my (unavoidable) use case, there may be concurrent 
> dynamic removes and adds of servers which may eventually have id collisions. 
> When this occurs, there is no good way to determine if the server (given an 
> id collision) that we want to remove is the right server.
> To support my use case, I propose that we add a tag field to the server 
> string.
> For my specific use case, this tag field will be used to store a uuid as a 
> string.
> So for example:
> server.1=127.0.0.1:1234:1236:participant;0.0.0.0:1237;743b9d23-85cb-45b1-8949-930fdabb21f0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to