[
https://issues.apache.org/jira/browse/ZOOKEEPER-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127759#comment-14127759
]
some one commented on ZOOKEEPER-2031:
-------------------------------------
For the -1 on the core tests. I'm seeing that it passes on my local tree for
the 3.5 branch (but also fails on trunk):
junit.run:
[junit] Running org.apache.zookeeper.server.quorum.ReconfigRecoveryTest
[junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 185.97 sec
junit.run:
[junit] Running org.apache.zookeeper.test.ReconfigTest
[junit] Tests run: 11, Failures: 0, Errors: 0, Time elapsed: 116.01 sec
Any ideas on what could have changed from 3.5 to trunk that might cause my
change to fail on trunk?
> 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)
