We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The current implementation of creating a snapshot is only executed after handle_committed_normal_entry.
handle_committed_normal_entry
I think there could be better ways.
For example, we can implement the following policies:
Create a snapshot when the size of the FSM exceeds a specific threshold. Generate a snapshot when the number of log entries surpasses a certain count.
Note: snapshot contains several metadata configuring the cluster, so wrong implementation of this would break the consistency of the raft loop.
snapshot
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
The current implementation of creating a snapshot is only executed after
handle_committed_normal_entry
.I think there could be better ways.
For example, we can implement the following policies:
Create a snapshot when the size of the FSM exceeds a specific threshold.
Generate a snapshot when the number of log entries surpasses a certain count.
Note:
snapshot
contains several metadata configuring the cluster, so wrong implementation of this would break the consistency of the raft loop.The text was updated successfully, but these errors were encountered: