Sriharsha Chintalapani created KAFKA-1844:
---------------------------------------------
Summary: Topic message.max.bytes can be larger than the
replica.fetch.max.bytes
Key: KAFKA-1844
URL: https://issues.apache.org/jira/browse/KAFKA-1844
Project: Kafka
Issue Type: Bug
Reporter: Sriharsha Chintalapani
Assignee: Sriharsha Chintalapani
This bug is related to KAFKA-1273. Kaka Broker on startup checks to see if the
configured replica.fetch.max.bytes >= message.max.bytes. But users can override
message.max.bytes per topic and there is no such validation happening for per
topic message.max.bytes. If the users configured message.max.bytes >
replica.fetch.max.bytes , followers won't be able to fetch data.
[~junrao] suggested " I was thinking that one way is to just disallow
customizing max.message.size per topic. Such customization may break downstream
consumers like MirrorMaker. I am not sure if there is a strong use case for the
per topic customization."
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
