CRZbulabula opened a new pull request, #17975: URL: https://github.com/apache/iotdb/pull/17975
## Description This PR adds hot-reload support for several cluster runtime configuration items managed by ConfigNode: - `heartbeat_interval_in_ms` - `continuous_query_min_every_interval_in_ms` - `schema_region_group_extension_policy` and `data_region_group_extension_policy` - `default_schema_region_group_num_per_database` and `default_data_region_group_num_per_database` - `schema_region_per_data_node` and `data_region_per_data_node` - `read_consistency_level` The implementation updates ConfigNode and DataNode hot-reload paths, removes stale cached configuration snapshots from region extension and read-consistency paths, and reschedules heartbeat-related ConfigNode services when the heartbeat interval changes. Region-per-DataNode changes trigger max region group recalculation only on the current ConfigNode leader. Load-balancing related parameters were also reviewed. Region extension policies and region-per-DataNode limits now support hot reload. `region_group_allocate_policy` and Ratis auto leader-balance settings remain restart-only because the corresponding balancer/allocator instances are selected during service initialization. ## Testing - `mvn spotless:apply -pl iotdb-core/confignode` - `mvn spotless:apply -pl iotdb-core/datanode` - `mvn spotless:apply -pl integration-test -P with-integration-tests` - `mvn compile -pl iotdb-core/confignode,iotdb-core/datanode -am -DskipTests -DskipUTs` - `mvn verify -DskipUTs -Dit.test=IoTDBSetConfigurationIT -DfailIfNoTests=false -Dfailsafe.failIfNoSpecifiedTests=false -Drat.skip=true -pl integration-test -am -P with-integration-tests` - `git diff --check` -- 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]
