[KAFKA-16224] Fix handling of deleted topic when auto-committing before revocation

• Type: Sub-task
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 3.8.0
• Component/s: clients, consumer
• Labels: client-transitions-issues kip-848-client-support
• Assignee: Bruno Cadonna
• Reporter: Lianet Magrans
• Created: 05/Feb/24 16:51
• Updated: 25/Mar/24 20:00
• Resolved: 25/Mar/24 20:00

Description

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 (meaning that we would effectively consider UnknownTopicOrPartitionException as non-retriable, even though it extends RetriableException, only when committing offsets before revocation as part of this task)
Note that legacy coordinator behaviour around this seems to be the same as the new consumer currently has, tracked with a related issue given that it would require a separate fix for the legacy consumer.

Issue Links

• is related to: KAFKA-16235 auto commit still causes delays due to retriable UNKNOWN_TOPIC_OR_PARTITION
• links to: GitHub Pull Request #15581