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

   ## Description
   
   Backport of #18496 to `dev/1.3`.
   
   When ConfigNode cannot provide a registered Pipe plugin JAR, DataNode 
startup currently fails. This change lets startup continue in a degraded state:
   
   - unsuccessful or malformed batch responses retry each plugin individually;
   - one unavailable JAR no longer blocks healthy plugins in the same batch;
   - JAR save and plugin registration failures are isolated;
   - unavailable plugins are skipped while the remaining plugins continue 
loading.
   
   The `dev/1.3` branch predates the plugin-loading error metadata and i18n 
message-source infrastructure used by `master`, so those master-only parts of 
#18496 are intentionally omitted from this compatibility backport.
   
   ## Recovery
   
   Missing plugin JARs are not polled after startup. After restoring a JAR on 
ConfigNode, restart the affected DataNode to retry startup loading.
   
   ## Validation
   
   - `mvn spotless:apply -pl iotdb-core/datanode`
   - Checkstyle: 0 violations
   - Spotless check: passed
   - `git diff --check`
   - Added focused tests for batch fallback, JAR-count mismatch fallback, and 
isolated save failure.
   - `mvn test -pl iotdb-core/datanode -Dtest=PipeAgentLauncherTest` reached 
module compilation but could not run the test because the existing workspace 
has unrelated stale cross-module/generated-source dependencies (for example 
missing ConfigNode thrift and node-commons symbols).
   
   Cherry-picked from `8a789d09a6046691b3b6003740c48334a0b79aa4`.
   
   This PR has:
   - [x] been self-reviewed.


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