You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Mirza Aliev (Jira)" <ji...@apache.org> on 2021/09/28 11:39:00 UTC
[jira] [Created] (IGNITE-15632) Investigate jraft's BallotBox
optimisation in case of removing peer
Mirza Aliev created IGNITE-15632:
------------------------------------
Summary: Investigate jraft's BallotBox optimisation in case of removing peer
Key: IGNITE-15632
URL: https://issues.apache.org/jira/browse/IGNITE-15632
Project: Ignite
Issue Type: Improvement
Reporter: Mirza Aliev
{{org.apache.ignite.raft.jraft.core.BallotBox#commitAt}} method contains comment from jraft developers about optimization which commits uncommitted logs in case of decreasing of quorum. This optimization is not proven, needs to be investigated.
Comment:
{noformat}
// When removing a peer off the raft group which contains even number of
// peers, the quorum would decrease by 1, e.g. 3 of 4 changes to 2 of 3. In
// this case, the log after removal may be committed before some previous
// logs, since we use the new configuration to deal the quorum of the
// removal request, we think it's safe to commit all the uncommitted
// previous logs, which is not well proved right now
{noformat}
Ticket was created after the decomposition of https://issues.apache.org/jira/browse/IGNITE-14832
See todo in {{org.apache.ignite.raft.jraft.core.BallotBox#commitAt}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)