jt2594838 opened a new pull request, #18821: URL: https://github.com/apache/iotdb/pull/18821
## Description During DataNode shutdown, SchemaEngine can clear a schema region while its validation lock is still registered. An in-flight internal timeseries creation request then dereferences the missing region during quota validation and returns INTERNAL_SERVER_ERROR (305). Check region availability in the shared timeseries prevalidation method and return the retryable NO_AVAILABLE_REGION_GROUP (906) status before accessing the region. Add matching English and Chinese messages. Existing validation and consensus writes remain unchanged when the region is available. ## Validation - Reproduced both single-device and batch failures before the fix: expected status 906, received 305. - `mvn spotless:apply test -pl iotdb-core/datanode -am -Drat.skip=true -Dtest=RegionWriteExecutorTest -Dsurefire.failIfNoSpecifiedTests=false`: passed, 4 tests with no failures, errors, or skips. New tests cover single/batch creation, ordinary/Pipe requests, SimpleConsensus/Ratis, and available/missing regions. - Full-reactor `test-compile -DskipTests -Drat.skip=true`, with and without `-P with-zh-locale`: DataNode and ConfigNode compiled successfully in both locales. Both builds stopped at distribution because the server, CLI, and ConfigNode SNAPSHOT ZIP dependencies were unavailable. - `git diff --check`: passed. No full cluster shutdown stress test was performed. This PR has: - [x] been self-reviewed. - [x] added comments explaining the shutdown lifecycle constraint. - [x] updated the prevalidation method documentation. - [x] added unit tests covering the changed behavior. Key changed classes: `RegionWriteExecutor`, `RegionWriteExecutorTest`, and both locale versions of `DataNodeQueryMessages`. -- 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]
