[
https://issues.apache.org/jira/browse/KAFKA-17294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-17294.
------------------------------------
Fix Version/s: 4.0.0
Resolution: Fixed
> Handle retriable errors when fetching offsets in new consumer
> -------------------------------------------------------------
>
> Key: KAFKA-17294
> URL: https://issues.apache.org/jira/browse/KAFKA-17294
> Project: Kafka
> Issue Type: Bug
> Components: clients, consumer
> Affects Versions: 3.7.0, 3.8.0
> Reporter: Lianet Magrans
> Assignee: TengYao Chi
> Priority: Major
> Labels: kip-848-client-support
> Fix For: 4.0.0
>
>
> The new consumer CommitRequestManager fails with a fatal KafkaException
> whenever it receives an unexpected error in the OffsetFetch response, even if
> the error is retriable. See
> https://github.com/apache/kafka/blob/837684a1b9b3bad244613211e90b67cf9170fb44/clients/src/main/java/org/apache/kafka/clients/consumer/internals/CommitRequestManager.java#L1009-L1011
> This was initially implemented like this to maintain the behaviour of the
> Classic consumer, where the ConsumerCoordinator would do the same when
> handling the OffsetFetchResponse. That behaviour is being updated for the
> legacy coordinator as part of KAFKA-17279, to retry on all retriable errors.
> We should review and update in the commitRequestManager to align with this,
> and retry on all retriable errors, which seems sensible when fetching
> offsets.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
