fix: fix some panic error when use replication#865
Merged
hezhangjian merged 1 commit intomainfrom Apr 20, 2025
Merged
Conversation
Signed-off-by: xiangyu5632 <[email protected]>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #865 +/- ##
==========================================
+ Coverage 76.72% 76.79% +0.06%
==========================================
Files 668 668
Lines 141536 141569 +33
==========================================
+ Hits 108597 108711 +114
+ Misses 26574 26508 -66
+ Partials 6365 6350 -15 🚀 New features to boost your workflow:
|
hezhangjian
approved these changes
Apr 20, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
When you use openGemini replication mode, a panic may occur after a period of normal system running. The reason is that when reading the raft log file, the read-write lock used causes the file offset to be incorrect, which ultimately prevents the WAL data from being cleaned up normally. The WAL file may become larger and larger, but the data will still normally be synchronized between replicas.