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

   ## Root cause
   
   The test set the unsupported consensus implementation through the common 
configuration, so both ConfigNode and DataNode received it. ConfigNode failed 
its startup check first. DataNode then failed to fetch the system configuration 
and exited during startup; the observed `255` was the low 8 bits of that 
secondary process exit status. The failure follows the node startup path and is 
not caused by random ConfigNode/DataNode startup ordering.
   
   ## Fix
   
   Start a valid 1C1D cluster, stop the DataNode, change only its persisted 
`data_region_consensus_protocol` to the unsupported implementation, restart it, 
and assert the low 8 bits of its `ILLEGAL_PARAMETER` exit status. Clean up the 
cluster in `finally`.
   
   ## Validation
   
   - `mvn clean verify -DskipUTs 
-Dit.test=IoTDBCustomizedClusterIT#testStartWithWrongConfig 
-DfailIfNoTests=false -Dfailsafe.failIfNoSpecifiedTests=false -pl 
integration-test -am -P DailyIT -P with-integration-tests -Drat.skip=true`: 1 
test passed.
   - `mvn spotless:apply -pl integration-test -P with-integration-tests 
-Drat.skip=true`: passed.
   - `git diff --check`: passed.
   


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