nielifeng commented on PR #11271:
URL: https://github.com/apache/seatunnel/pull/11271#issuecomment-5139942834

   Runtime verification completed for head 
`4496c6e4886976ca36945642d2f997bcdcb501a9` against current `dev` 
`7e25769a8e6fa4de5f65f20fa62e0e3dcc32993c`.
   
   Environment and flow:
   
   - 3-master / 3-worker Zeta cluster, 24 total slots
   - MySQL-CDC two-table baseline, 10 rows per table
   - checkpoint interval 5 seconds, parallelism 1
   - savepoint stop, restore with one table removed from the current config
   - post-restore increment written to both the retained and removed source 
tables
   
   Verification results:
   
   - targeted tests: `IncrementalSplitTest,IncrementalSplitStateTest` -> 3 
tests, 0 failures, 0 errors
   - deployed REST metadata: `gitCommitAbbrev=4496c6e`
   - baseline snapshot: source/sink `10/10` for both tables
   - savepoint: `SAVEPOINT_DONE`
   - restored job: `RUNNING`
   - final checkpoints: `39 triggered / 39 completed / 0 failed / 0 in progress`
   - retained table: source/sink `10 -> 11`
   - removed table: source `10 -> 11`, sink stayed `10`
   - Worker runtime split after restore contained only the retained table in 
all three relevant structures:
     - `tableIds`
     - `checkpointTables`
     - `historyTableChanges`
   - no `Can't obtain schema` or restore ERROR was observed
   
   For comparison, current `dev` already produced a retained-only `tableIds` 
list in this non-destructive scenario, but still carried both tables in 
`checkpointTables` and `historyTableChanges`. The PR removed that stale 
metadata at the actual reader restore path.
   
   Conclusion: no runtime blocker found on this head. The cluster was rolled 
back to the default `dev` release after the test and verified at 3 workers, 
24/24 unassigned slots, and zero running/pending/failed jobs. Current GitHub 
checks are green.
   


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