I could be misunderstanding, but I think the main difference in behavior is that between when changingEnsemble gets set to true and when the ensemble change completes, new writes continue to use the old ensemble whereas with the old machinery they would have optimistically used the new one. In both cases, we have to delay acks until the ensemble change is complete, but with this variant we may have to wait to resend writes for entries written since the ensemble change began which didn't get aQ responses from unchanged indexes. Am I understanding that correctly @ivankelly ?
[ Full content available at: https://github.com/apache/bookkeeper/pull/1646 ] This message was relayed via gitbox.apache.org for [email protected]
