You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "dengziming (Jira)" <ji...@apache.org> on 2022/01/05 02:39:00 UTC

[jira] [Commented] (KAFKA-13570) Fallback of unsupported versions of ApiVersionsRequest and RequestHeader?

    [ https://issues.apache.org/jira/browse/KAFKA-13570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17468965#comment-17468965 ] 

dengziming commented on KAFKA-13570:
------------------------------------

I don't  think it's a simple problem for a Server to properly handle a higher version RPC from a Client. So it's the responsibility of client to do it, most Kafka client will fallback to older version RPC on an UnsupportedVersionException, but it's not granted.

> Fallback of unsupported versions of ApiVersionsRequest and RequestHeader?
> -------------------------------------------------------------------------
>
>                 Key: KAFKA-13570
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13570
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Fredrik Arvidsson
>            Priority: Minor
>
> I've gone through the protocol documentation and the source code, but I can't find any explicit documentation stating how clients and brokers are handling the scenario when the client sends higher versions of ApiVersionsRequest and RequestHeader which the broker doesn't understand. I've seen hints in discussions that the broker would fallback to returning version 0 of the ApiVersionsResponse in this scenario.
> Are there any documentation that explains these scenarios?



--
This message was sent by Atlassian Jira
(v8.20.1#820001)