[
https://issues.apache.org/jira/browse/BOOKKEEPER-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009832#comment-14009832
]
Ivan Kelly commented on BOOKKEEPER-759:
---------------------------------------
Well, we have the zookeeper registration. Maybe we could not remove from the
ensemble until we see that the bookie has lost it's zookeeper session (which
would cause it to crash anyhow, which brings me to another thing. We shouldn't
crash the bookie if it loses the session. It only needs it for GC and this ties
uptime to zookeeper, if the zookeeper cluster is down for some time, we should
be able to continue writing to bookies as long as the bookies are available).
> bookkeeper: delay ensemble change if it doesn't break ack quorum requirement
> ----------------------------------------------------------------------------
>
> Key: BOOKKEEPER-759
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-759
> Project: Bookkeeper
> Issue Type: Improvement
> Components: bookkeeper-client
> Reporter: Sijie Guo
> Assignee: Sijie Guo
> Fix For: 4.4.0
>
>
> flag to allow delay ensemble change. if that is set to change, will not do
> ensemble change until it breaks ack quorum requirement
--
This message was sent by Atlassian JIRA
(v6.2#6252)
