[
https://issues.apache.org/jira/browse/HBASE-23157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16955490#comment-16955490
]
Duo Zhang commented on HBASE-23157:
-----------------------------------
[~binlijin] After checking the code, we do have a wal.sync when preparing a
flush, see here
https://github.com/apache/hbase/blob/4d414020bb3bfd7f214d2a599426be700df772b2/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java#L2689
So maybe there are other bugs?
Have you enabled in memory compaction?
> 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)
