-
Notifications
You must be signed in to change notification settings - Fork 142
Allow WAL replaying on some corrupted WAL files (e.g. after DB was killed) #5111
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
Conversation
Benchmark ResultMaster commit hash:
|
Codecov ReportAttention: Patch coverage is
❌ Your patch status has failed because the patch coverage (60.00%) is below the target coverage (80.00%). You can increase the patch coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## master #5111 +/- ##
=======================================
Coverage 87.61% 87.61%
=======================================
Files 1403 1403
Lines 63594 63596 +2
Branches 7522 7522
=======================================
+ Hits 55715 55720 +5
+ Misses 7850 7847 -3
Partials 29 29 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
7cc3f12
to
c336b2e
Compare
Benchmark ResultMaster commit hash:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
8a4daa5
to
f5e5ddd
Compare
Benchmark ResultMaster commit hash:
|
Description
After a kuzu process is killed, the WAL may be in an incomplete state. This PR stops an error from being reported if we are replaying an incomplete WAL. Instead the replaying logic will be:
Fixes #5016
Contributor agreement