li3zhi4 commented on PR #11633: URL: https://github.com/apache/seatunnel/pull/11633#issuecomment-5268427004
@DanielLeens — an update on the CI status you flagged in round 11 (the `kafka-connector-it (11)` failure on the `73989d5fb` head): **Root cause confirmed — a Kafka topic-readiness race, not a code defect.** The failure was `UnknownTopicOrPartitionException` in `KafkaSourceSplitEnumerator.getTopicInfo`: leader visibility in the admin metadata view (which `waitForKafkaTopicsReady` checks) does not guarantee the broker the job's own Kafka client connects to has finished assigning/propagating the partition leader. The new head `0dbea3718` applies your round-6 **Option B** suggestion: before submitting the job, the test now produces and consumes a throwaway record on the source topic to force metadata propagation end-to-end, then deletes it via `deleteRecords` so it does not leak into the job's `earliest`-start read. This is test-only; no production code touched. **Verified locally:** `KafkaJsonDefaultValueIT` e2e 1/1 passed on this head. The `unit-test (8, windows)` `JobStateEventTest` Hazelcast failure from the same run remains a pre-existing, unrelated engine-server flake (confirmed by you in round 11), so the feature-relevant jobs are green. Branch is up to date with `dev`. -- 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]
