[
https://issues.apache.org/jira/browse/KAFKA-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14225215#comment-14225215
]
Patrick Lucas commented on KAFKA-1273:
--------------------------------------
I ran into this on 0.8.1.1.
Perhaps if you override message.max.bytes in the config file it complains on
startup, but Kafka allows you to modify this value per-topic.
I have a topic with a higher value of message.max.bytes, and it was very
difficult to diagnose why its replicas could not stay in sync.
> Brokers should make sure replica.fetch.max.bytes >= message.max.bytes
> ---------------------------------------------------------------------
>
> Key: KAFKA-1273
> URL: https://issues.apache.org/jira/browse/KAFKA-1273
> Project: Kafka
> Issue Type: Bug
> Components: replication
> Affects Versions: 0.8.0
> Reporter: Dong Zhong
> Assignee: Sriharsha Chintalapani
> Labels: newbie
>
> If message.max.bytes is larger than replica.fetch.max.bytes，followers can't
> fetch data from the leader and will incur endless retry. And this may cause
> high network traffic between followers and leaders.
> Brokers should make sure replica.fetch.max.bytes >= message.max.bytes by
> adding a sanity check, or throw an exception.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
