Following up on #4324 which adds the syncShareCommits option for share consumer containers, we should consider adding support for AcknowledgementCommitCallback when async commits are used.
Currently when syncShareCommits=false, the container calls commitAsync() (PR #4379) but there's no visibility into whether those commits succeed or fail. The Kafka ShareConsumer API provides setAcknowledgementCommitCallback() for this purpose.
Proposal:
• When async commits are enabled, register a default callback that logs failures
• Optionally expose a way for users to provide their own callback via ContainerProperties for custom error handling
This would give users better observability when opting into async commits for higher throughput.
Related: #4324, PR #4379
Following up on #4324 which adds the
syncShareCommitsoption for share consumer containers, we should consider adding support forAcknowledgementCommitCallbackwhen async commits are used.Currently when
syncShareCommits=false, the container callscommitAsync()(PR #4379) but there's no visibility into whether those commits succeed or fail. The KafkaShareConsumerAPI providessetAcknowledgementCommitCallback()for this purpose.Proposal:
• When async commits are enabled, register a default callback that logs failures
• Optionally expose a way for users to provide their own callback via
ContainerPropertiesfor custom error handlingThis would give users better observability when opting into async commits for higher throughput.
Related: #4324, PR #4379