[
https://issues.apache.org/jira/browse/ZOOKEEPER-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127930#comment-14127930
]
some one commented on ZOOKEEPER-2031:
-------------------------------------
I looked around the other builds on Jenkins and it looks like these failures
have been happening already and are unrelated to my patch:
testPortChange:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2294/testReport/
--> This one is just a doc change and the core test errors seem to be
ignored:
https://issues.apache.org/jira/browse/ZOOKEEPER-1660
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2310/testReport/
--> Again these core test errors seem to be ignored here:
https://issues.apache.org/jira/browse/ZOOKEEPER-1962
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2311/testReport/
--> Same here: https://issues.apache.org/jira/browse/ZOOKEEPER-2024
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2300/testReport/
testCurrentServersAreObserversInNextConfig:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2315/testReport/
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2308/testReport/
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2301/testReport/
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2299/testReport/
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2296/testReport/
> 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.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)
