-
Notifications
You must be signed in to change notification settings - Fork 9.1k
HDFS-17710. Don't add journal edits to cache until after persisted to storage #7296
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
HDFS-17710. Don't add journal edits to cache until after persisted to storage #7296
Conversation
|
@ZanderXu @aswinmprabhu since you were most recently working with the Journal code. |
|
💔 -1 overall
This message was automatically generated. |
4604794 to
e609064
Compare
|
🎊 +1 overall
This message was automatically generated. |
e609064 to
4682ddf
Compare
|
💔 -1 overall
This message was automatically generated. |
4682ddf to
1f280d2
Compare
|
💔 -1 overall
This message was automatically generated. |
1f280d2 to
5b1e6eb
Compare
|
💔 -1 overall
This message was automatically generated. |
5b1e6eb to
36ac76b
Compare
|
💔 -1 overall
This message was automatically generated. |
|
We're closing this stale PR because it has been open for 100 days with no activity. This isn't a judgement on the merit of the PR in any way. It's just a way of keeping the PR queue manageable. |
36ac76b to
04cdd07
Compare
|
🎊 +1 overall
This message was automatically generated. |
Description of PR
Update the process of JournalNodes journaling new edits to persist edits to disk before adding them to the edit cache. This prevents standby and observer nodes from accidentally reading transactions from the edit cache when tailing logs that have not actually been durably persisted, making the standby or observer have in invalid state thinking the latest committed transaction is higher than it should be.
How was this patch tested?
New UT using a new fault injector method to simulate a disk write failure.
For code changes:
LICENSE,LICENSE-binary,NOTICE-binaryfiles?