kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dana Powers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-3550) Broker does not honor MetadataRequest api version; always returns v0 MetadataResponse
Date Sat, 28 Oct 2017 19:07:00 GMT

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

Dana Powers commented on KAFKA-3550:
------------------------------------

Does not happen on brokers 0.10+ . Feel free to resolve. I think this issue is useful primarily
to document the behavior for anyone attempting to build clients compatible with brokers prior
to ApiVersions api support.

> Broker does not honor MetadataRequest api version; always returns v0 MetadataResponse
> -------------------------------------------------------------------------------------
>
>                 Key: KAFKA-3550
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3550
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.8.0, 0.8.1.1, 0.8.2.2, 0.9.0.1
>            Reporter: Dana Powers
>            Assignee: Grant Henke
>
> To reproduce:
> Send a MetadataRequest (api key 3) with incorrect api version (e.g., 1234).
> The expected behavior is for the broker to reject the request as unrecognized.
> Broker (incorrectly) responds with MetadataResponse v0.
> The problem here is that any request for a "new" MetadataRequest (i.e., KIP-4) sent to
an old broker will generate an incorrect response.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message