Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BACKPORT] Improve the Raft snapshotting optimization #15068

Conversation

metanet
Copy link
Contributor

@metanet metanet commented May 21, 2019

If there is at least one follower with unknown match index, its log can
be close to the leader's log so we are keeping the old log entries.
Otherwise, we will keep the log entries until the minimum match index
that is bigger than (commitIndex - maxNumberOfLogsToKeepAfterSnapshot).
If there is no such follower (all of the minority followers are far
behind), then there is no need to keep the old log entries.

Backport of #15062

If there is at least one follower with unknown match index, its log can
be close to the leader's log so we are keeping the old log entries.
Otherwise, we will keep the log entries until the minimum match index
that is bigger than (commitIndex - maxNumberOfLogsToKeepAfterSnapshot).
If there is no such follower (all of the minority followers are far
behind), then there is no need to keep the old log entries.
@metanet metanet added this to the 3.12.1 milestone May 21, 2019
@metanet metanet requested a review from mdogan May 21, 2019 15:27
@metanet metanet merged commit f089d9c into hazelcast:maintenance-3.x May 23, 2019
@mmedenjak mmedenjak added the Source: Internal PR or issue was opened by an employee label Apr 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Module: CP Subsystem Source: Internal PR or issue was opened by an employee
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants