Caideyipi commented on PR #19051:
URL: https://github.com/apache/iotdb/pull/19051#issuecomment-6681184793

   This CI failure was caused by a test fixture topology mismatch. All six 
`IoTDBPipeTransferRecoveryIT` errors in [job 
127702284283](https://github.com/apache/iotdb/actions/runs/42159729717/job/127702284283)
 were status 1003 during database/timeseries setup, before the recovery 
assertions ran.
   
   `HighPerformanceMode` supplies SchemaRegion replication 3 and DataRegion 
replication 2, while this class explicitly starts only one DataNode in each 
cluster. `RegionBalancer` correctly rejects allocation when the available 
DataNode count is below the replication factor.
   
   Commit `125c9659a8f81c643462b2a51fa7e8867f5bf601` explicitly sets both 
replication factors to 1 for sender and receiver before initialization. The six 
scenarios and their assertions are unchanged; no production fix is needed for 
this failure.
   
   Validation: Windows / JDK 17, `MultiClusterIT2DualTreeAutoEnhanced`, 
`ClusterConfigurations=HighPerformanceMode,HighPerformanceMode`. A focused 
`clean verify -pl integration-test -am` rebuilt the required source dependency 
closure with compilation caching disabled. **6 tests passed, 0 failures, 0 
errors, 0 skipped; Maven exit code 0.** Scoped Spotless and whitespace checks 
also passed. Earlier remote attempts were blocked before compilation by 
dependency/network availability and are not counted as test results. The full 
suite, Linux execution at this head, and Chinese locale were not verified in 
this investigation.
   
   Inspected revision: `989dd054fc3a0269f30c24988837ef9d09b51f4e`. Final local 
commit, confirmed source-branch head, and confirmed PR head: 
`125c9659a8f81c643462b2a51fa7e8867f5bf601`.
   
   This was a focused CI investigation, not a complete independent review of 
the combined PR. The PR remains a draft pending that review.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to