zookeeper-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enrico Olivelli (Jira)" <j...@apache.org>
Subject [jira] [Updated] (ZOOKEEPER-2031) Support tagging a QuorumServer
Date Fri, 06 Sep 2019 15:46:08 GMT

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Enrico Olivelli updated ZOOKEEPER-2031:
---------------------------------------
    Fix Version/s:     (was: 3.5.6)

> 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
>            Priority: Major
>             Fix For: 3.6.0, 3.5.7
>
>         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
(v8.3.2#803003)

Mime
View raw message