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

   ## Description
   
   Split LOAD transactions write to a region's write peer but retain progress 
generated by the coordinator. When those nodes differ, IoTConsensusV2 filters 
the imported TsFile out of replication because its progress contains no local 
node ID. Even with a local coordinator, progress allocated before PREPARE can 
fall behind intervening writes. Other replicas can therefore miss imported 
data, including after cluster restart.
   
   Assign fresh receiving-node progress when COMMIT imports each staged TsFile, 
and serialize it into the resource file before publishing the import. Other 
consensus protocols retain the prepared progress. Regression tests check 
replication eligibility after resource recovery, ordering after an intervening 
write, and the non-V2 behavior.
   
   ## Validation
   
   - The two V2 regression tests fail before the fix; the non-V2 control passes.
   - `LoadTsFileManagerTest`, `LoadTsFileTableSchemaTest`, and 
`LoadTsFileResumeTest`: 34 tests passed.
   - `IoTDBPipeDataSinkIT#testSinkTsFileFormat10` and 
`IoTDBPipeLifeCycleIT#testDoubleLiving`: both passed with dual IoTConsensusV2 
Batch clusters and again with dual Stream clusters (4 IT executions, including 
both cluster restarts).
   - The integration-test reactor package completed successfully.
   - Spotless, Checkstyle, and `git diff --check` passed.
   


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