[
https://issues.apache.org/jira/browse/KAFKA-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414281#comment-15414281
]
Tomasz Trębski commented on KAFKA-4022:
---------------------------------------
Yes, that generally my concern here that current behaviour is not that
intuitive as I'd suspect it to be.
I don't know, maybe I am just thinking out loud here and throwing an idea that
does not make any sense.
Though, thx for helping me out and let me know if you plan on including my
comments in kafka (a.k.a. make TopicCommand use actual setting in this [or
other] case).
BTW. Actually I have to stick with 0.9.0.0 because of the python-kafka library
which we use and which version (that we can use as restricted by openstack
requirements) support only kafka up to 0.9.0.0. I am aware of the force flag
but that was introduced/released with kafka 0.10.0.0.
BTW2. If you'd ever need it, expect module in ansible is great :)
Cheers.
> 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
> Assignee: Vahid Hashemian
>
> 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)
