Feature : Add manual offset commit option for batch consumers#290
Merged
Vruttant1403 merged 2 commits intoJun 24, 2026
Merged
Conversation
Riya-bhardwaj
force-pushed
the
feature/batch-consumer-manual-commit
branch
from
June 17, 2026 11:07
7ef2959 to
cdf5d12
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Batch consumers commit Kafka offsets via background auto-commit (
enable.auto.commit=true), which commits on a timer independently of batch processing. If a consumer dies after an offset is auto-committed but before the batch is processed (and its failures enqueued for retry), those messages are lost. This has caused message loss in production.Solution
Add an opt-in per-batch-route flag
:manual-commit-enabled(defaultfalse). When enabled, auto-commit is turned off and offsets are committed withcommitSynconly after a batch is processed — guaranteeing at-least-oncedelivery. Commit failures are logged + metered (
ziggurat.batch.consumption.offset.commit) but don't halt the loop.Default
falsekeeps existing behaviour unchanged — fully backward compatible.