HBASE-23181 Blocked WAL archive: "LogRoller: Failed to schedule flush of XXXX, because it is not online on us" #742
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.
… of XXXX, because it is not online on us"
Fix is moving a line in HRegion to close a gap that would allow an old
edit to sneak into the backing SequenceIdAccounting datastructure.
The below line gets moved up before wal.startCacheFlush:
We change the LogRoller constructor to remove redundant param. It will
also call the temporary,ugly purge method (To be removed if we've found
fix...). Because of constructor chagne, need to change also
TestFailedAppendAndSync, TestWALLockup, TestAsyncFSWAL &
WALPerformanceEvaluation.java
We add a purge method called when something is wrong to AbstractFSWAL.java
Need to be removed when 'fix' is in place.
SequenceIdAccounting gets a purge method called when we find lagging
records.