You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Chia-Ping Tsai (Jira)" <ji...@apache.org> on 2026/04/08 05:22:00 UTC
[jira] [Resolved] (KAFKA-20119) Clarify that `Consumer#unsubscribe` does not trigger auto-commit
[ https://issues.apache.org/jira/browse/KAFKA-20119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chia-Ping Tsai resolved KAFKA-20119.
------------------------------------
Fix Version/s: 4.4.0
Resolution: Fixed
> Clarify that `Consumer#unsubscribe` does not trigger auto-commit
> ----------------------------------------------------------------
>
> Key: KAFKA-20119
> URL: https://issues.apache.org/jira/browse/KAFKA-20119
> Project: Kafka
> Issue Type: Improvement
> Components: clients, consumer, docs
> Reporter: Chia-Ping Tsai
> Assignee: TaiJuWu
> Priority: Minor
> Fix For: 4.4.0
>
>
> I suggest adding a note to clarify that unsubscribe() does not guarantee a commit, which could lead to duplicate processing if offsets are not manually committed.
> {code:java}
> Note: Unlike close(), this method does not guarantee that pending offsets are committed before unsubscribing, even if enable.auto.commit is enabled. To avoid duplicate processing upon re-joining, it is recommended to explicitly call {@link #commitSync()} before invoking this method
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)