-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.2.1
-
Fix Version/s: 3.0.0-alpha-1, 2.3.1, 2.4.0, 2.2.6
-
Component/s: regionserver, wal
-
Labels:None
-
Hadoop Flags:Reviewed
Durability.ASYNC_WAL do not wait wal sync and commit mvcc ahead. So when region start flush may get a large flushedSeqId and later wal process buffer entry and put a small unflushedSequenceIds for this region again.
- is related to
-
HBASE-22539 WAL corruption due to early DBBs re-use when Durability.ASYNC_WAL is used
-
- Resolved
-
-
HBASE-23181 Blocked WAL archive: "LogRoller: Failed to schedule flush of XXXX, because it is not online on us"
-
- Resolved
-
-
HBASE-16721 Concurrency issue in WAL unflushed seqId tracking
-
- Closed
-
- links to