[
https://issues.apache.org/jira/browse/BOOKKEEPER-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009561#comment-14009561
]
Ivan Kelly commented on BOOKKEEPER-759:
---------------------------------------
I was thinking about this a bit more. We shouldn't wait for ack requirement to
be broken. The point of separating write quorum and ack quorum was that there
would not be latency spikes when a bookie fails. Rather, I think we should
perhaps wait a little so we don't ensemble change straight away, and then if we
can't change ensemble (i.e. there's not enough to rebuild the ensemble), keep
going as long as ack quorum isn't broken.
> 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)
