hutiefang76 opened a new issue, #12959:
URL: https://github.com/apache/seatunnel/issues/12959

   ### Search before asking
   
   - [x] I searched the issues and found no report of this test-ordering 
failure. #11884 / #11885 describe the original latest-stop implementation, 
which is already merged.
   
   ### What happened
   
   The existing 
`MysqlCDCStopModeSpecificIT.testMysqlCdcInitialStartupWithLatestStop` failed in 
[this JDK 17 CI 
job](https://github.com/hutiefang76/seatunnel/actions/runs/39772122616/job/119806031879).
 It expected `latest-stop` for row 21, but still read `bulk` when the 60-second 
value wait expired.
   
   The attached Failsafe XML contains snapshot progress until just before the 
case ended. After removing duplicated log output, 105 completed split exports 
contained 1,995 of the fixture's 2,000 rows. The last export was at 
23:54:21.570 UTC and the case ended at 23:54:21.940 UTC.
   
   `runLatestStopStartupMode` currently checks the final binlog value before 
waiting for the bounded job to reach `FINISHED`. `HybridSplitAssigner` assigns 
the incremental split after snapshot completion. The value wait can therefore 
expire while the snapshot is still progressing. This evidence does not 
establish that an in-bound CDC update was lost.
   
   I am working on a test-only follow-up: wait for `FINISHED` and check the 
existing job exit result before checking final sink values. The existing 
60/120-second bounds, data assertions and fixture data stay unchanged. I will 
validate all seven stop-mode cases in this class; patched integration 
validation is not complete yet.
   
   ### SeaTunnel Version
   
   Observed at `91d1078a3790cf0bcdfbda5cd235c28ec8a95219`. The affected helper 
and relevant assigner/configuration paths also match dev 
`6b63aca173eb8c056db0b78a87539aec3e4ad1a5`.
   
   ### SeaTunnel Config
   
   The existing 
[mysqlcdc_stop_mode_latest.conf](https://github.com/apache/seatunnel/blob/6b63aca173eb8c056db0b78a87539aec3e4ad1a5/seatunnel-e2e/seatunnel-connector-v2-e2e/connector-cdc-mysql-e2e/src/test/resources/mysqlcdc_stop_mode_latest.conf)
 with `startup_mode=initial`, `stop.mode=latest`, `snapshot.split.size=20`, 
parallelism 1 and the existing 2,000-row initial fixture.
   
   ### Running Command
   
   The linked CI job ran the MySQL CDC E2E module with:
   
   ```shell
   ./mvnw -B -T 1 verify -DskipUT=true -DskipIT=false 
-Dlicense.skipAddThirdParty=true -Dskip.ui=true --no-snapshot-updates -pl 
:connector-cdc-mysql-e2e -am -Pci
   ```
   
   For focused validation, add `-Dit.test=MysqlCDCStopModeSpecificIT 
-Dfailsafe.failIfNoSpecifiedTests=false` and set `RUN_ENGINES=zeta`. That 
focused patched run has not completed yet.
   
   ### Error Exception
   
   Awaitility timed out after 60 seconds in `runLatestStopStartupMode`: 
expected `latest-stop`, actual `bulk`, with assertion message `post-snapshot 
update must be synced`.
   
   ### Zeta or Flink or Spark Version
   
   Zeta from the source revision above. MySQL 8.0.43.
   
   ### Java or Scala Version
   
   Outer CI JDK 17; engine container `eclipse-temurin:11-jdk`.
   
   ### Are you willing to submit PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct).
   
   Investigation and the proposed patch are AI-assisted with Codex and DeepSeek.
   


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