Caideyipi opened a new pull request, #19353: URL: https://github.com/apache/iotdb/pull/19353
## Summary Shorten DataRegion write-lock hold time during historical Pipe source startup while preserving startup lifecycle and history semantics. - Flush and copy consistent TsFile and deletion snapshots while holding the DataRegion write lock. - Check and pin resources outside that lock; refresh only a replaced partition once and release TsFile and modification-file pins independently on failure. - Keep realtime startup before historical startup and keep historical `start()` synchronous. ## Example Before: DataRegion 43 has 100,138 out-of-order files. Starting six Pipe historical sources scans and pins the history while holding the write lock, so concurrent writes wait about 18 seconds. After: the lock covers the required flush and consistent snapshots; per-resource checks and pinning proceed after release, reducing write-lock occupancy while preserving historical filtering, ordering, and deletion handling. ## Testing - `mvn spotless:apply -P with-integration-tests -pl iotdb-core/datanode` passed; zero files changed. - `mvn clean test -pl iotdb-core/datanode -am -Dtest=PipeHistoricalDataRegionTsFileAndDeletionSourceTest -Dsurefire.failIfNoSpecifiedTests=false` passed; 31 tests. -- 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]
