[
https://issues.apache.org/jira/browse/HBASE-28037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17770228#comment-17770228
]
Hudson commented on HBASE-28037:
--------------------------------
Results for branch branch-2.4
[build #626 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/626/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/626/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/626/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/626/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/626/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}
> Replication stuck after switching to new WAL but the queue is empty
> -------------------------------------------------------------------
>
> Key: HBASE-28037
> URL: https://issues.apache.org/jira/browse/HBASE-28037
> Project: HBase
> Issue Type: Bug
> Components: Replication
> Affects Versions: 3.0.0-alpha-4, 2.5.5
> Reporter: Xiaolin Ha
> Assignee: Xiaolin Ha
> Priority: Blocker
> Fix For: 2.4.18, 2.5.6
>
>
> When the speed of consuming replication WALs is high, and there are something
> wrong when creating new WAL, the swith of replcation source reader to new WAL
> in the queue may happen before the new WAL is created, then the replcation
> will stuck since it can not consume the new WALs soon afterwards anymore.
> Restarting the RS that replication stucking can make the replication recover.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
