[
https://issues.apache.org/jira/browse/ZOOKEEPER-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16147696#comment-16147696
]
Fangmin Lv edited comment on ZOOKEEPER-2879 at 8/30/17 6:14 PM:
----------------------------------------------------------------
(Sorry for the lately reply, was oncall and handling prod issues)
[~dbenediktson] and [~hanm], thanks for the comments, the main purpose is to
make the server maintain easier, we have more than 500 observers, which are
also frequently being replaced and decommed, which makes the tool hard to work
correctly. Also, we're using the highest 1 byte as the server id, which is
limited the number of servers to be less than 256, which is too small for us.
The issue do exist for non unique session id, we're thinking of ways to solve
it.
was (Author: lvfangmin):
(Sorry for the lately reply, was oncall and handling prod issues)
[~dbenediktson] and [~hanm], thanks for the comments, the main purpose is to
make the server maintain easier, we have more than 500 observers, which are
also frequently being replaced and decommed, which makes the tool hard to work
correctly.
The issue do exist for non unique session id, we're thinking of ways to solve
it.
> Adding observers dynamically without server id
> ----------------------------------------------
>
> Key: ZOOKEEPER-2879
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2879
> Project: ZooKeeper
> Issue Type: Improvement
> Components: quorum
> Affects Versions: 3.6.0
> Reporter: Fangmin Lv
> Assignee: Fangmin Lv
>
> Dynamic config requires observer has unique server id, which means we cannot
> simply add observer with dynamic server id -1. For large observer cluster,
> it's much more easier to add observer without unique server id if it doesn't
> need to be promoted to participant. Also, it will make dynamic config more
> efficient, we don't need to store and send the long list of observers during
> re-config.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
