[
https://issues.apache.org/jira/browse/HBASE-23157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16951854#comment-16951854
]
Lijin Bin edited comment on HBASE-23157 at 10/15/19 11:43 AM:
--------------------------------------------------------------
I think the first choice is to force a wal.sync before wal.startCacheFlush,
this impact the flush/write performance.
The second choice that we can clear the region's sequenceId info when LogRoller
find the region is not open on this rs now, but master will still have the WARN
log.
May be there are other choice i do not find now.
was (Author: aoxiang):
I think the first choice is to force a wal.sync before wal.startCacheFlush,
this impact the flush speed.
The second choice that we can clear the region's sequenceId info when LogRoller
find the region is not open on this rs now, but master will still have the WARN
log.
May be there are other choice i do not find now.
> 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)
