Duo Zhang created HBASE-30095:
---------------------------------
Summary: Remove duplicated startMiniDFSCluste call in TestZooKeeper
Key: HBASE-30095
URL: https://issues.apache.org/jira/browse/HBASE-30095
Project: HBase
Issue Type: Sub-task
Components: test
Reporter: Duo Zhang
Sonnet 4.5(4.6?) summary
TestZooKeeper
Problem Identified:
Line 78 had a duplicate call to TEST_UTIL.startMiniDFSCluster(2)
This violated the "can only create one" constraint and caused HDFS namespace
conflicts when tests ran in parallel
Why it was flaky:
✅ Local/isolated runs: Worked because no leftover HDFS state
❌ CI/parallel runs: Failed when other ZooKeeper tests ran first, leaving behind
HDFS data with incompatible namespaceID
Fix Applied:
Removed the duplicate call on line 78. The test now properly:
Starts Mini DFS Cluster (line 71)
Starts Mini ZK Cluster (line 72)
Configures settings (lines 73-77)
Done! (no duplicate cluster start)
This matches the pattern used in other similar tests like TestClusterBootOrder
and aligns with the comment's intent: "Test we can first start the ZK cluster
by itself."
The test should now be stable across both local and CI environments. You can
verify by running the test suite again to ensure TestZooKeeper no longer fails
with InconsistentFSStateException.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
