[IOTDB-1583] Raft log failed to be committed in cluster version#3832
Merged
neuyilan merged 11 commits intoapache:masterfrom Aug 31, 2021
Merged
[IOTDB-1583] Raft log failed to be committed in cluster version#3832neuyilan merged 11 commits intoapache:masterfrom
neuyilan merged 11 commits intoapache:masterfrom
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
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.
The bug is caused by a raft log is oversize.
When the size of a log is bigger than buffer (default 16MB),it can not be persistent due to the
BufferOverflowException. But the log has committed in memory, we will commit the same log again.So,we should check the size of the log at the entrance to avoid that leader will send this log to followers.
BTW, this case may cause the next plan failed in server mode. Because we didn't clear the buffer, it still contains some information from the previous log.