[
https://issues.apache.org/jira/browse/HBASE-23157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16955685#comment-16955685
]
Lijin Bin edited comment on HBASE-23157 at 10/21/19 1:51 AM:
-------------------------------------------------------------
[~zhangduo]
The wal.sync is called after wal.startCacheFlush(encodedRegionName,
flushedFamilyNamesToSeq); , we need to call it before wal.startCacheFlush.
Also this can reproduce in test, you can get it which i upload in the patch.
was (Author: aoxiang):
[~zhangduo]
The wal.sync is called after wal.startCacheFlush(encodedRegionName,
flushedFamilyNamesToSeq); , we need to call it before wal.startCacheFlush.
> WAL unflushed seqId tracking may wrong when Durability.ASYNC_WAL is used
> ------------------------------------------------------------------------
>
> Key: HBASE-23157
> URL: https://issues.apache.org/jira/browse/HBASE-23157
> Project: HBase
> Issue Type: Bug
> Components: regionserver, wal
> Affects Versions: 2.2.1
> Reporter: Lijin Bin
> Assignee: Lijin Bin
> Priority: Major
> Attachments: HBASE-23157-master-v1.patch
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
