You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Jason Gustafson (Jira)" <ji...@apache.org> on 2022/09/13 02:41:00 UTC
[jira] [Created] (KAFKA-14224) Consumer should auto-commit prior to cooperative partition revocation
Jason Gustafson created KAFKA-14224:
---------------------------------------
Summary: Consumer should auto-commit prior to cooperative partition revocation
Key: KAFKA-14224
URL: https://issues.apache.org/jira/browse/KAFKA-14224
Project: Kafka
Issue Type: Bug
Reporter: Jason Gustafson
With the old "eager" reassignment logic, we always revoked all partitions prior to each rebalance. When auto-commit is enabled, a part of this process is committing current position. Under the cooperative logic, we defer revocation until after the rebalance, which means we can continue fetching while the rebalance is in progress. However, when reviewing KAFKA-14196, we noticed that there is no similar logic to commit offsets prior to this deferred revocation. This means that cooperative consumption is more likely to lead to have duplicate consumption even when there is no failure involved.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)