[
https://issues.apache.org/jira/browse/KAFKA-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226851#comment-14226851
]
Sriharsha Chintalapani commented on KAFKA-1273:
-----------------------------------------------
[~nehanarkhede] this doesn't look straight forward as TopicCommand doesn't know
what values are in server.properties. It calls LogConfig to validate which
doesn't have access to this info. One way of doing this is to pass
server.properties to the TopicCommand which doesn't look intuitive. Another
option is to add an api that return a configResponse which contains all the
server.properties that user defined along with defaults. Please let me know
what you think about these approaches.
> 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)
