[
https://issues.apache.org/jira/browse/KAFKA-16224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lianet Magrans updated KAFKA-16224:
-----------------------------------
Priority: Critical (was: Major)
> Fix handling of deleted topic when auto-committing before revocation
> --------------------------------------------------------------------
>
> Key: KAFKA-16224
> URL: https://issues.apache.org/jira/browse/KAFKA-16224
> Project: Kafka
> Issue Type: Sub-task
> Components: clients, consumer
> Reporter: Lianet Magrans
> Assignee: Lianet Magrans
> Priority: Critical
> Labels: client-transitions-issues, kip-848-client-support
> Fix For: 3.8.0
>
>
> Current logic for auto-committing offsets when partitions are revoked will
> retry continuously when getting UNKNOWN_TOPIC_OR_PARTITION, leading to the
> member not completing the revocation in time. We should consider this as an
> indication of the topic being deleted, and in the context of committing
> offsets to revoke partitions, we should abort the commit attempt and move on
> to complete and ack the revocation (effectively considering
> UnknownTopicOrPartitionException as non-retriable in this context)
> Note that legacy coordinator behaviour around this seems to be the same as
> the new consumer currently has.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
