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 2020/06/22 03:09:00 UTC
[jira] [Commented] (HBASE-24594) testReplicationStatusSink last
applied op ts comparison failure
[ https://issues.apache.org/jira/browse/HBASE-24594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141660#comment-17141660 ]
Hudson commented on HBASE-24594:
--------------------------------
Results for branch branch-2
[build #2713 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2713/]: (/) *{color:green}+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/2713/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2713/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2713/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/2713/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}
> testReplicationStatusSink last applied op ts comparison failure
> ---------------------------------------------------------------
>
> Key: HBASE-24594
> URL: https://issues.apache.org/jira/browse/HBASE-24594
> Project: HBase
> Issue Type: Test
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.1, 2.4.0
>
>
> The failure to compare timestamp of last applied op with RS start is not a permanent failure, nor does it seem flaky but while running all tests as part of 2.3 RC0 validation, I did encounter the failure:
>
> [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 29.212 s <<< FAILURE! - in org.apache.hadoop.hbase.replication.TestReplicationStatus[ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 29.212 s <<< FAILURE! - in org.apache.hadoop.hbase.replication.TestReplicationStatus[ERROR] org.apache.hadoop.hbase.replication.TestReplicationStatus.testReplicationStatusSink Time elapsed: 1.016 s <<< FAILURE!java.lang.AssertionError: expected:<1592477704810> but was:<1592477719964> at org.apache.hadoop.hbase.replication.TestReplicationStatus.testReplicationStatusSink(TestReplicationStatus.java:134)
>
> It seems we should allocate separate resources to testReplicationStatusSink: separate class, shutdown peer cluster (if running already), bring it up and check timestamp of lastAppliedOp, then proceed with remaining test i.e timestampsOfLastAppliedOp > timestampStarted within specific period of time soon after inserting some records.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)