Caideyipi opened a new pull request, #19051: URL: https://github.com/apache/iotdb/pull/19051
## Description Add six Pipe P0 recovery integration tests using shared dual-cluster fixtures and a deterministic Thrift fault relay: - Retain and drain backlog after every receiver DataNode becomes unavailable, without rescue writes. - Recover across the history/realtime handoff while historical transfer is still pending. - Reconcile multiple actual DataRegions and writers across a verified DataRegion leader transfer. - Retry a request rejected before forwarding without starving another Pipe. - Retry a persisted write after losing its successful response and verify the idempotent final state. - Exercise runtime queue backpressure, cross-Pipe isolation, STOP/START recovery, and DROP resource release. The tests compare business timestamps, values, payloads, and schema, then check bounded quiet drain and resource cleanup. ## Validation - Java sources were formatted with Google Java Format 1.28.0. - The focused workflow passed YAML, Bash, and embedded Python syntax checks; `git diff --check` passed. - Compilation and the six IT cases have not yet completed successfully. Independent review is pending; this PR intentionally remains a draft. - The `pipe_p0_only` workflow-dispatch input selects only `IoTDBPipeRecoveryIT` under `MultiClusterIT2DualTreeAutoEnhanced`. The workflow checks that all six cases ran without skips, errors, or failures and uploads their reports and cluster logs. - Automatic CI is skipped for this draft's current head commit. A focused manual run is requested instead of the full test matrix. Dispatches without this input retain the existing workflow behavior. This PR has: - [x] added integration tests. - [ ] been independently self-reviewed. - [ ] been tested successfully in a test IoTDB cluster. -- 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]
