[jira] [Commented] (KAFKA-598) decouple fetch size from max message size

["Stevo Slavic (JIRA)" <ji...@apache.org>]

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

Stevo Slavic commented on KAFKA-598:
------------------------------------

Curious, does new consumer coming in 0.9.0.0 allow easier detecting of "there's larger message then fetch size" situation, and using different fetch size for different requests programmatically?

> decouple fetch size from max message size
> -----------------------------------------
>
>                 Key: KAFKA-598
>                 URL: https://issues.apache.org/jira/browse/KAFKA-598
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.8.0
>            Reporter: Jun Rao
>            Assignee: Joel Koshy
>            Priority: Blocker
>              Labels: p4
>         Attachments: KAFKA-598-v1.patch, KAFKA-598-v2.patch, KAFKA-598-v3.patch
>
>
> Currently, a consumer has to set fetch size larger than the max message size. This increases the memory footprint on the consumer, especially when a large number of topic/partition is subscribed. By decoupling the fetch size from max message size, we can use a smaller fetch size for normal consumption and when hitting a large message (hopefully rare), we automatically increase fetch size to max message size temporarily.



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