[jira] [Resolved] (KAFKA-436) Multifetch response size overflow

["Jay Kreps (JIRA)" <ji...@apache.org>]

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

Jay Kreps resolved KAFKA-436.
-----------------------------
    Resolution: Fixed

This should be fixed as part of the response size issues being done for the new consumer.

> Multifetch response size overflow
> ---------------------------------
>
>                 Key: KAFKA-436
>                 URL: https://issues.apache.org/jira/browse/KAFKA-436
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.7.1, 0.8.0
>            Reporter: Gregoire Seux
>
> Fetchsize parameter is per partition in fetch requests. 
> This makes the size of response unpredicatable and thus might overflow.
> (original email : http://mail-archives.apache.org/mod_mbox/incubator-kafka-users/201208.mbox/%3C416A89FBBC95114F8B2D2E91781541E9638B201E%40SRVEX02.criteois.lan%3E   )
> Three propositions : 
> - fetch size is only a hint, broker will ensure that it won't overflow (maybe not sending too much data)
> - broker respect fetchsize as a global limit and not by partition
> - broker may not send data for all topics to avoid the overflow.
> Changing size to int64 could also decrease probablity of such event.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)