This repository was archived by the owner on Mar 4, 2024. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #250.
The fix ensures the log entry containing the uncommitted config entry is still present in case it has to be rolled back.
Draft: Investigating if this could lead to some form of "snapshot starvation" where a snapshot would never be taken when the config is being changed constantly.
Edit: I think it's possible to never take a snapshot with this addition to the code. The proper fix would be to keep a copy of the last committed configuration around and add that one to the snapshot. This again brings up the problem of the Raft API update #303 , because keeping a copy around will increase the size of
struct raft
.Edit2: We can probably work around the API limitation (for now), we could probably get the last committed config from the log if it's still there, and if it's not, we could get it from the previous snapshot. One of the 2 has to succeed.