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

   ## Summary
   
   - Add `testDeleteTimeSeriesReplicaConsistency()` integration test to verify 
that `DELETE TIMESERIES` operations are properly replicated across all DataNode 
replicas in a 3C3D IoTConsensusV2 cluster
   - The test reproduces the scenario from the historical deletion replication 
bug (fixed in #17329): deletion events missing `replicateIndex` were silently 
dropped by `IoTConsensusV2Processor`, causing schema inconsistency across 
replicas
   - Unify `INSERTION` constants across all test methods to use 3 columns 
(`speed`, `temperature`, `power`), replacing the prior 2-column variants
   
   ## Test Scenario
   
   1. Insert data with 3 measurements (`speed`, `temperature`, `power`) and 
flush
   2. Insert more data **without flush** (WAL-only entries, simulating 
in-flight data)
   3. `DELETE TIMESERIES root.sg.d1.speed`
   4. Flush to persist the deletion
   5. Wait for replication to complete (syncLag == 0) on all data region leaders
   6. Verify schema consistency on each DataNode independently via `SHOW 
TIMESERIES`
   7. Stop each DataNode one by one (triggers consensus pipe reconstruction + 
historical replay), verify all surviving nodes still show consistent schema — 
the deleted timeseries must be absent everywhere
   
   ## Test Plan
   
   - [x] `testDeleteTimeSeriesReplicaConsistency` added in both **stream** and 
**batch** mode subclasses
   - [ ] Run 
`IoTDBIoTConsensusV2Stream3C3DBasicIT.testDeleteTimeSeriesReplicaConsistency`
   - [ ] Run 
`IoTDBIoTConsensusV2Batch3C3DBasicIT.testDeleteTimeSeriesReplicaConsistency`
   - [ ] Verify existing tests `test3C3DWriteFlushAndQuery` and 
`testReplicaConsistencyAfterLeaderStop` still pass with unified 3-column 
insertions
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


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