[
https://issues.apache.org/jira/browse/HBASE-25349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17243427#comment-17243427
]
Hudson commented on HBASE-25349:
--------------------------------
Results for branch branch-2
[build #119 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/119/]:
(/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/119/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/119/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/119/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/119/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}
> [Flakey Tests] branch-2
> TestRefreshRecoveredReplication.testReplicationRefreshSource:141 Waiting
> timed out after [60,000] msec
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-25349
> URL: https://issues.apache.org/jira/browse/HBASE-25349
> Project: HBase
> Issue Type: Bug
> Components: flakies
> Reporter: Michael Stack
> Assignee: Michael Stack
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.4.0
>
>
> This one fails for me most times running locally.
> I added some debug (see the PR).
> In the test we look for old replication source to be non-zero long after it
> has been processed. The test gets stuck waiting.
> See here is where the table becomes available, after which we start expecting
> the old source replication queue to be non-zero.
> {{ 2020-12-01 20:02:52,400 INFO [Listener at localhost/56996]
> regionserver.TestRefreshRecoveredReplication(136): Available
> testReplicationRefreshSource}}
> But see here where the replication source has been removed before we get to
> the 'available' line above:
> {{2020-12-01 20:02:50,768 INFO
> [ReplicationExecutor-0.replicationSource,2-kalashnikov.attlocal.net,56950,1606881738045.replicationSource.shipperkalashnikov.attlocal.net%2C56950%2C1606881738045,2-kalashnikov.attlocal.net,56950,1606881738045]
> regionserver.ReplicationSourceManager(463): Done with the recovered queue
> 2-kalashnikov. attlocal.net,56950,1606881738045}}{{ }}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
