You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2023/03/15 14:49:00 UTC
[jira] [Created] (HBASE-27720) TestClusterRestartFailover is flakey
Nick Dimiduk created HBASE-27720:
------------------------------------
Summary: TestClusterRestartFailover is flakey
Key: HBASE-27720
URL: https://issues.apache.org/jira/browse/HBASE-27720
Project: HBase
Issue Type: Task
Components: test
Affects Versions: 2.5.4
Reporter: Nick Dimiduk
Assignee: Nick Dimiduk
I'm seeing failures like this in PR,
{noformat}
[ERROR] Failures:
[ERROR] org.apache.hadoop.hbase.master.TestClusterRestartFailoverSplitWithoutZk.test
[ERROR] Run 1: TestClusterRestartFailoverSplitWithoutZk>TestClusterRestartFailover.test:143 serverNode should be deleted after SCP finished expected null, but was:<d09295c85a7e,33451,1678875566216/SPLITTING/regionCount=0/lock=java.util.concurrent.locks.ReentrantReadWriteLock@1823f707[Write locks = 0, Read locks = 0]>
[ERROR] Run 2: TestClusterRestartFailoverSplitWithoutZk>TestClusterRestartFailover.test:147 serverCrashSubmittedCount(8) should be equal expected:<4> but was:<8>
[ERROR] Run 3: TestClusterRestartFailoverSplitWithoutZk>TestClusterRestartFailover.test:147 serverCrashSubmittedCount(12) should be equal expected:<4> but was:<12>
{noformat}
Looks like subsequent runs would have passed, but for the firm metric count assertion.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)