HDFS-17710. Don't add journal edits to cache until after persisted to storage #7296
+32
−3
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.
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-binary
files?