The GitHub Actions job "Flink Connector Kafka CI" on flink-connector-kafka.git/FLINK-36532-commit-offsets-on-close has failed. Run started by GitHub user sqd (triggered by sqd).
Head commit for run: c248b798f83d751c04c7fd73d38aeedf8231e066 / Han You <[email protected]> [FLINK-36532][Connectors/Kafka] Commit offsets on stop-with-savepoint Currently, the Kafka source commits the offsets of a completed checkpoint by queueing an asynchronous commit on the split fetcher. Stop-with-savepoint closes the reader right after the savepoint completes, and the fetcher shuts down without running the queued commit, so the savepoint's offsets never reach Kafka. With group.protocol=consumer, closing the consumer also drops a commit that is already in flight. This happens with and without --drain. The consumer group then lags behind the savepoint: lag monitoring is wrong, and a job that starts from the committed offsets instead of the savepoint re-reads records. This commit makes the reader commit the offsets of the latest completed checkpoint synchronously when it closes, unless their asynchronous commit has already finished. The commit runs on the fetcher thread as it closes the consumer, because only that thread may use the consumer. Offsets of a checkpoint that did not complete, and of the snapshot that DynamicKafkaSourceReader takes outside a checkpoint, are not committed. Generated-by: Claude Code (Claude Opus 5.5) Report URL: https://github.com/apache/flink-connector-kafka/actions/runs/38620961865 With regards, GitHub Actions via GitBox
