[HBASE-23157] WAL unflushed seqId tracking may wrong when Durability.ASYNC_WAL is used

• 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
• Hadoop Flags: Reviewed
• Assignee: Duo Zhang
• Reporter: Lijin Bin
• Created: 12/Oct/19 11:34
• Updated: 11/Aug/20 00:38
• Resolved: 10/Aug/20 03:06

Description

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.

Issue Links

• is related to: HBASE-22539 WAL corruption due to early DBBs re-use when Durability.ASYNC_WAL is used
• is related to: HBASE-23181 Blocked WAL archive: "LogRoller: Failed to schedule flush of XXXX, because it is not online on us"
• is related to: HBASE-16721 Concurrency issue in WAL unflushed seqId tracking
• links to: GitHub Pull Request #739
• links to: GitHub Pull Request #762