You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "PoAn Yang (Jira)" <ji...@apache.org> on 2024/10/08 00:51:00 UTC
[jira] [Commented] (KAFKA-17536) Ensure clear error message when "new" consumer used with incompatible cluster
[ https://issues.apache.org/jira/browse/KAFKA-17536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17887458#comment-17887458 ]
PoAn Yang commented on KAFKA-17536:
-----------------------------------
Hi [~kirktrue], if you're not working on this, may I take it? Is this about when `
group.coordinator.rebalance.protocols=classic` and consumer group uses `consumer`, we need to return better error message? Thanks.
> Ensure clear error message when "new" consumer used with incompatible cluster
> -----------------------------------------------------------------------------
>
> Key: KAFKA-17536
> URL: https://issues.apache.org/jira/browse/KAFKA-17536
> Project: Kafka
> Issue Type: Improvement
> Components: clients, consumer
> Affects Versions: 3.9.0
> Reporter: Kirk True
> Priority: Critical
> Labels: kip-848-client-support
> Fix For: 4.0.0
>
>
> In Kafka 4.0, by default the consumer uses the updated consumer group protocol defined in KIP-848. When the consumer is used with a cluster that does not support (or is not configured to use) the new protocol, the consumer will get an unfriendly error about unavailable APIs. Since this error could be the user's first impression when attempting to upgrade to 4.0, we need to make sure that the error is very clear about the remediation steps (set the group.protocol to CLASSIC on the client or upgrade and enable the new protocol on the cluster).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)