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/05/08 22:07:12 UTC

[jira] [Updated] (KAFKA-3579) TopicCommand references outdated consumer property fetch.message.max.bytes

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

Ismael Juma updated KAFKA-3579:
-------------------------------
       Resolution: Fixed
    Fix Version/s: 0.10.0.0
           Status: Resolved  (was: Patch Available)

Issue resolved by pull request 1239
[https://github.com/apache/kafka/pull/1239]

> TopicCommand references outdated consumer property fetch.message.max.bytes 
> ---------------------------------------------------------------------------
>
>                 Key: KAFKA-3579
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3579
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Jun Rao
>            Assignee: Vahid Hashemian
>              Labels: newbie
>             Fix For: 0.10.0.0
>
>
> TopicCommand gives the following warning.
> *****************************************************************************************************
> *** WARNING: you are creating a topic where the the max.message.bytes is greater than the consumer ***
> *** default. This operation is potentially dangerous. Consumers will get failures if their        ***
> *** fetch.message.max.bytes < the value you are using.                                            ***
> *****************************************************************************************************
> - value set here: 1300000
> - Default Consumer fetch.message.max.bytes: 1048576
> - Default Broker max.message.bytes: 1000012
> fetch.message.max.bytes is used in the old consumer. We should reference 
> max.partition.fetch.bytes in the new consumer instead.



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