Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
Reviewed
Description
We added FLUSH, REGION CLOSE events into WAL, for each those events the region SeqId is bumped.
The issue comes from region close operation. Because when opening a region, we use flushed SeqId from store files while after store flush during region close we still write COMMIT_FLUSH, REGION_CLOSE events etc which respectively bump up SeqId. Therefore, the region opening SeqId is lower than it should be.