CRZbulabula opened a new pull request, #17878: URL: https://github.com/apache/iotdb/pull/17878
### Description This PR fixes a ConfigNode race observed when creating SchemaRegionGroups and immediately allocating SchemaPartitions. The RegionGroup creation procedure could finish after load cache and route priority had been activated, while the local PartitionInfo used by partition allocation had not exposed the new RegionGroup yet. That made getOrCreateSchemaPartition report no available SchemaRegionGroups even though the RegionGroup creation logs looked successful. Changes: - Wait for newly created RegionGroups to become visible in PartitionInfo before returning success from RegionGroup allocation. - Propagate RegionGroup persistence failures from CreateRegionGroupsProcedure instead of continuing to activate RegionGroups after a failed consensus write. - Reject RemoveDataNode earlier when data_replication_factor is 1 or an existing DataRegion has only one replica, with a clearer user-facing and log message. - Add IT coverage for the RemoveDataNode single-replica error message. ### Tests - mvn compile -pl iotdb-core/confignode - mvn verify -DskipUTs -Drat.skip=true -Dit.test=IoTDBRemoveDataNodeNormalIT#failWhenDataReplicationFactorIsOneUseSQL -DfailIfNoTests=false -Dfailsafe.failIfNoSpecifiedTests=false -pl integration-test -am -PClusterIT -P with-integration-tests - mvn verify -DskipUTs -Drat.skip=true -Dit.test=IoTDBRawQueryWithoutValueFilterWithDeletionIT#selectAllAlignedWithoutValueFilterTest -DfailIfNoTests=false -Dfailsafe.failIfNoSpecifiedTests=false -pl integration-test -am -PClusterIT -P with-integration-tests -- 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]
