Caideyipi opened a new pull request, #18934:
URL: https://github.com/apache/iotdb/pull/18934

   ## Description
   
   ConfigNode could apply SimpleConsensus plans before their WAL records were 
durable and report successful node registration after failed consensus writes. 
This backport persists WAL records before execution and propagates registration 
failures, rolling back incomplete DataNode/AINode registration.
   
   Backport #17609 (`08380be95ae82bffc9e1aa8adf7cc1a92eb027ee`) to `dev/1.3`.
   
   - Roll back failed WAL appends, force operations, and plan execution; fix 
log rotation, recovery indexes, and writer shutdown.
   - Keep ConfigNode registration pending for retry after persistence failure 
and notify success after both registration plans persist.
   - Preserve successful snapshots when pipe listener processing fails, and fix 
partition counting and maintenance task snapshots.
   
   Adapted to the 1.3 consensus request, snapshot loading, and runtime 
configuration APIs. Includes the EN/ZH message constants used by this fix with 
locale source selection in the ConfigNode module.
   
   ## Validation
   
   All 44 reactor modules passed the English build and Chinese test 
compilation. The four affected test classes passed all 19 regression tests.
   
   ```shell
   mvn spotless:apply -pl iotdb-core/confignode
   mvn -nsu test 
'-Dtest=ConfigRegionStateMachineTest,NodeManagerRegistrationTest,NodeInfoTest,PartitionInfoTest'
 '-Dsurefire.failIfNoSpecifiedTests=false'
   mvn -nsu test-compile -DskipTests -P with-zh-locale
   ```
   
   Also verified EN/ZH key and placeholder parity for all 21 message constants 
and `git diff --check origin/dev/1.3`.
   
   This PR has:
   
   - [x] been self-reviewed.
   - [x] added regression tests for WAL failures, registration failures, WAL 
replay, and partition counting.
   


-- 
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