You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2021/05/21 12:00:00 UTC
[jira] [Commented] (HBASE-25897) TestRetainAssignmentOnRestart is
flaky after HBASE-25032
[ https://issues.apache.org/jira/browse/HBASE-25897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17349172#comment-17349172 ]
Hudson commented on HBASE-25897:
--------------------------------
Results for branch master
[build #298 on builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/298/]: (x) *{color:red}-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/master/298/General_20Nightly_20Build_20Report/]
(/) {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/master/298/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/master/298/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
--Failed when running client tests on top of Hadoop 3. [see log for details|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/298//artifact/output-integration/hadoop-3.log]. (note that this means we didn't check the Hadoop 3 shaded client)
> TestRetainAssignmentOnRestart is flaky after HBASE-25032
> --------------------------------------------------------
>
> Key: HBASE-25897
> URL: https://issues.apache.org/jira/browse/HBASE-25897
> Project: HBase
> Issue Type: Bug
> Components: Region Assignment
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.5.0
>
>
> The problem is that, we will only assign regions to a region server after its first regionServerReport, so after restart, the region may be assigned before the region server is ready to take regions, and then cause the test to fail.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)