[ 
https://issues.apache.org/jira/browse/HBASE-23157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174445#comment-17174445
 ] 

Hudson commented on HBASE-23157:
--------------------------------

Results for branch branch-2.3
        [build #205 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/205/]: 
(x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/205/General_20Nightly_20Build_20Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- Something went wrong running this stage, please [check relevant console 
output|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/205//console].


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/205/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/205/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> 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)

Reply via email to