[
https://issues.apache.org/jira/browse/HBASE-28114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778208#comment-17778208
]
Hudson commented on HBASE-28114:
--------------------------------
Results for branch master
[build #929 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/929/]:
(/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/929/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/929/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/929/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}
> Add more comments to explain why replication log queue could never be empty
> for normal replication queue
> --------------------------------------------------------------------------------------------------------
>
> Key: HBASE-28114
> URL: https://issues.apache.org/jira/browse/HBASE-28114
> Project: HBase
> Issue Type: Bug
> Components: Replication
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 2.6.0, 3.0.0-beta-1
>
>
> In HBASE-28037, [~Xiaolin Ha] found that there could be a very small window
> that even for a normal replication source, its queue could be empty.
> This is because we will only enqueue the wal file to the queue in
> postLogRoll, where the old WAL writer has already been closed, so if the
> replication is fast enough, we could reach the end of the queue before
> enqueuing the new wal file.
> The code for branch-2+ has been refactored a lot so we opened a new issue for
> fixing this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
