Caideyipi opened a new pull request, #17877: URL: https://github.com/apache/iotdb/pull/17877
### What changed - Drop the processor and sink stages before cleaning up the source stage, so a dropped pipe stops consuming and forwarding events first. - Make historical source close visible before synchronized cleanup, allowing concurrent supply/start paths to stop returning events after drop. - Track pinned historical TsFile resources explicitly and release only those pinned resources during drop cleanup. ### Why For pure historical sync, DROP PIPE can remove ConfigNode metadata before DataNode task cleanup finishes. The historical source close path could then wait behind a concurrent supply() call while processor/sink continued forwarding historical TsFile events, so SHOW PIPES was empty but the receiver still observed data transfer. ### Verification - mvn -pl iotdb-core/datanode spotless:apply - mvn -pl iotdb-core/datanode compile reached javac after checkstyle and spotless passed, then failed due local native memory/pagefile exhaustion; generated hs_err/replay files were removed. -- 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]
