Caideyipi opened a new pull request, #19094: URL: https://github.com/apache/iotdb/pull/19094
## Description A history-only pipe can finish scanning a replica before earlier writes have reached it. Since its realtime source only emits heartbeats, those writes are then omitted permanently. Wait for a fixed IoTConsensus replication boundary before taking the DataRegion write lock and starting historical extraction. The positive `source.history.wait-for-replication.timeout-ms` option defaults to 30000 ms and shares one waiting budget across peers. Timeout or interruption fails startup. Snapshot mode receives the same barrier; realtime data sources keep their existing startup behavior, and the existing node-migration wait retains its completion semantics. Keep row-level time filtering for historical TsFiles until the files close and their time bounds are complete. If acquiring a historical file event's resource reference fails, retain the queue entry, pin, and replicate index for retry instead of consuming the file and advancing progress. Regression tests cover replication boundaries and timeout handling, realtime-source isolation with history enabled and disabled, unclosed-file time filtering, and resource-reference retry and close behavior. ## Validation - English full-reactor `clean install -DskipTests` passed using a fresh isolated Maven repository; TsFile was built from source. - The six related consensus and DataNode test classes passed: 57 tests, 0 failures, 0 errors, 0 skipped. - Chinese full-reactor `clean test-compile -DskipTests -P with-zh-locale` compiled the changed node-commons, consensus, and DataNode modules, including their tests. The command exited nonzero later in distribution because `test-compile` does not install the server, CLI, and ConfigNode ZIP artifacts required by that packaging POM. - Spotless passed with the integration-test profile on the changed modules. -- 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]
