You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Lianet Magrans (Jira)" <ji...@apache.org> on 2023/12/19 16:46:00 UTC
[jira] [Created] (KAFKA-16032) Review inconsistent error handling of OffsetFetch and OffsetCommit responses
Lianet Magrans created KAFKA-16032:
--------------------------------------
Summary: Review inconsistent error handling of OffsetFetch and OffsetCommit responses
Key: KAFKA-16032
URL: https://issues.apache.org/jira/browse/KAFKA-16032
Project: Kafka
Issue Type: Sub-task
Components: clients, consumer
Reporter: Lianet Magrans
OffsetFetch and OffsetCommit handle errors separately. There are 2 issues to review around this:
- The logic is duplicated for some errors that are treated similarly (ex. NOT_COORDINATOR)
- Some errors are not handled similarly in both requests (ex. COORDINATOR_NOT_AVAILABLE handled and retried for OffsetCommit but not OffsetFetch). Note that the specific errors handled by each request were kept the same as in the legacy ConsumerCoordinator but this should be reviewed, in an attempt to handle the same errors, in the same way, whenever possible.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)