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

["Duo Zhang (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-23157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Duo Zhang resolved HBASE-23157.
-------------------------------
    Fix Version/s: 2.2.6
                   2.4.0
                   2.3.1
                   3.0.0-alpha-1
     Hadoop Flags: Reviewed
       Resolution: Fixed

Pushed to branch-2.2+.

Thanks all for reviewing.

> 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: Duo Zhang
>            Priority: Major
>             Fix For: 3.0.0-alpha-1, 2.3.1, 2.4.0, 2.2.6
>
>         Attachments: HBASE-23157-UT.patch, HBASE-23157-master-v1.patch, TestMaxFlushedSeqId.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)