You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Sean Quah (Jira)" <ji...@apache.org> on 2024/08/05 17:08:00 UTC
[jira] [Updated] (KAFKA-17267) New group coordinator can return REQUEST_TIMED_OUT for OFFSET_FETCHes
[ https://issues.apache.org/jira/browse/KAFKA-17267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Quah updated KAFKA-17267:
------------------------------
Description:
Under some circumstances, the new group coordinator can return {{REQUEST_TIMED_OUT}} errors in response to {{OFFSET_FETCH}} requests.
However, the client (ConsumerCoordinator) does not handle this error code and treats it as non-retryable. For compatibility with older clients, we can map {{REQUEST_TIMED_OUT}} to {{{}NOT_COORDINATOR{}}}.
Similar to KAFKA-16386.
was:
Under some circumstances, the new group coordinator can return {{REQUEST_TIMED_OUT}} errors in response to {{OFFSET_FETCH}} requests.
However, the client (ConsumerCoordinator) does not handle this error code and treats it as non-retryable. For compatibility with older clients, we can map {{REQUEST_TIMED_OUT}} to {{NOT_COORDINATOR}}.
> New group coordinator can return REQUEST_TIMED_OUT for OFFSET_FETCHes
> ---------------------------------------------------------------------
>
> Key: KAFKA-17267
> URL: https://issues.apache.org/jira/browse/KAFKA-17267
> Project: Kafka
> Issue Type: Bug
> Components: group-coordinator
> Reporter: Sean Quah
> Priority: Minor
>
> Under some circumstances, the new group coordinator can return {{REQUEST_TIMED_OUT}} errors in response to {{OFFSET_FETCH}} requests.
> However, the client (ConsumerCoordinator) does not handle this error code and treats it as non-retryable. For compatibility with older clients, we can map {{REQUEST_TIMED_OUT}} to {{{}NOT_COORDINATOR{}}}.
>
> Similar to KAFKA-16386.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)