[
https://issues.apache.org/jira/browse/HBASE-23157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16950242#comment-16950242
]
Duo Zhang commented on HBASE-23157:
-----------------------------------
So the problem here is that the unflushedSequenceId go backward so this may
cause data loss? IIRC we will write a flush marker into WAL before actually
flush? We do not use this one And what's more, for ASYNC_WAL we actually do not
guarantee that there are no data loss?
> 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)
