You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ismael Juma (JIRA)" <ji...@apache.org> on 2016/04/12 21:11:25 UTC

[jira] [Commented] (KAFKA-3550) Broker does not honor MetadataRequest api version; always returns v0 MetadataResponse

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

Ismael Juma commented on KAFKA-3550:
------------------------------------

cc [~granthenke]

> 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
>
> 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.3.4#6332)