[ https://issues.apache.org/jira/browse/KAFKA-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15412542#comment-15412542 ]
Vahid Hashemian commented on KAFKA-4022: ---------------------------------------- [~kornicameis...@gmail.com] I believe this is simply a warning. If you try to create a topic with modified settings as you suggested you receive this warning message, but the topic you are trying to create will be created. I tried it with the broker's setting of 2000000 and topic setting of 1500000. The message simply warns about issues that could occur if consumers don't change their maximum possible fetch sizes. I hope I did not misunderstand the issue you raised. > TopicCommand is using default max.message.bytes instead of broker's setting > --------------------------------------------------------------------------- > > Key: KAFKA-4022 > URL: https://issues.apache.org/jira/browse/KAFKA-4022 > Project: Kafka > Issue Type: Bug > Components: admin > Affects Versions: 0.9.0.0, 0.9.0.1, 0.10.0.0 > Environment: Linux testHost 3.10.0-229.el7.x86_64 #1 SMP Fri Mar 6 > 11:36:42 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux > Reporter: Tomasz Trębski > > Even though it is possible to configure brokers to support message that are > bigger than 1MB, admin tool to create topics won't accept the one that's size > is above 1,000,000 bytes. > Responsible line can be found under this link: > [TopicCommand|https://github.com/apache/kafka/blob/trunk/core/src/main/scala/kafka/admin/TopicCommand.scala#L366] > Console output also seems to be confirm that: > ERROR > {code:title=console_otuput|borderStyle=solid} > **************************************************************************************************** > *** WARNING: you are creating a topic where the max.message.bytes is greater > than the broker *** > *** default. This operation is dangerous. There are two potential side > effects: *** > *** - Consumers will get failures if their fetch.message.max.bytes < the > value you are using *** > *** - Producer requests larger than replica.fetch.max.bytes will not > replicate and hence have *** > *** a higher risk of data loss > *** > *** You should ensure both of these settings are greater than the value set > here before using *** > *** this topic. > *** > **************************************************************************************************** > - value set here: 1048576 > - Default Broker replica.fetch.max.bytes: 1048576 > - Default Broker max.message.bytes: 1000012 > - Default Consumer fetch.message.max.bytes: 1048576 > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)