CRZbulabula opened a new pull request, #17950: URL: https://github.com/apache/iotdb/pull/17950
## Description This patch fixes a flaky timeout in `IoTDBPerDatabaseRegionGroupAllocationIT` when creating DataRegionGroups with the GCR allocation policy. The test only validates DataRegion replica placement, but it disabled IoTConsensus leader balancing. With leader balancing disabled, newly created IoTConsensus DataRegionGroups can remain with `leaderId=-1` until `CreateRegionGroupsProcedure` waits close to the procedure timeout. Under GCR, region creation may take long enough for the outer procedure wait to time out and return `CREATE_REGION_ERROR` even though all replicas were created successfully. Enable IoTConsensus leader balancing for this replica-placement test so RegionGroups become ready promptly, without changing replica placement assertions. The assertion for DataPartition creation now also includes the returned TSStatus for easier diagnosis. ## Tests - `mvn spotless:apply -pl integration-test -P with-integration-tests` - `mvn verify -Drat.skip=true -DskipUTs -Dit.test=IoTDBPerDatabaseRegionGroupAllocationIT -DfailIfNoTests=false -Dfailsafe.failIfNoSpecifiedTests=false -pl integration-test -am -PClusterIT -P with-integration-tests` Note: local full RAT validation was blocked by an unrelated `.claude/scheduled_tasks.lock` file in the working tree, so the focused IT verification used `-Drat.skip=true`. -- 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]
