You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2017/06/19 17:31:00 UTC

[jira] [Resolved] (KAFKA-5465) FetchResponse v0 does not return any messages when max_bytes smaller than v2 message set

     [ https://issues.apache.org/jira/browse/KAFKA-5465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Gustafson resolved KAFKA-5465.
------------------------------------
    Resolution: Won't Fix

For the reasons mentioned by Ismael above, we've decided not to fix this for now. If anyone has concerns, please leave a comment and we will reconsider.

> FetchResponse v0 does not return any messages when max_bytes smaller than v2 message set 
> -----------------------------------------------------------------------------------------
>
>                 Key: KAFKA-5465
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5465
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.11.0.0
>            Reporter: Dana Powers
>            Assignee: Jason Gustafson
>            Priority: Blocker
>             Fix For: 0.11.0.1
>
>
> In prior releases, when consuming uncompressed messages, FetchResponse v0 will return a message if it is smaller than the max_bytes sent in the FetchRequest. In 0.11.0.0 RC0, when messages are stored as v2 internally, the response will be empty unless the full MessageSet is smaller than max_bytes. In some configurations, this may cause old consumers to get stuck on large messages where previously they were able to make progress one message at a time.
> For example, when I produce 10 5KB messages using ProduceRequest v0 and then attempt FetchRequest v0 with partition max bytes = 6KB (larger than a single message but smaller than all 10 messages together), I get an empty message set from 0.11.0.0. Previous brokers would have returned a single message.



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