[
https://issues.apache.org/jira/browse/KAFKA-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631785#comment-14631785
]
Edward Ribeiro commented on KAFKA-2338:
---------------------------------------
Hi [~ewencp], as this my first official Kafka patch (yay!) it should have some
misunderstandings or plain errors (I was particularly in doubt about the
logging of a useful message by the broker's replica fetcher). Please, whenever
you have time, see if it's okay. Thanks!
> Warn users if they change max.message.bytes that they also need to update
> broker and consumer settings
> ------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-2338
> URL: https://issues.apache.org/jira/browse/KAFKA-2338
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8.2.1
> Reporter: Ewen Cheslack-Postava
> Fix For: 0.8.3
>
> Attachments: KAFKA-2338.patch
>
>
> We already have KAFKA-1756 filed to more completely address this issue, but
> it is waiting for some other major changes to configs to completely protect
> users from this problem.
> This JIRA should address the low hanging fruit to at least warn users of the
> potential problems. Currently the only warning is in our documentation.
> 1. Generate a warning in the kafka-topics.sh tool when they change this
> setting on a topic to be larger than the default. This needs to be very
> obvious in the output.
> 2. Currently, the broker's replica fetcher isn't logging any useful error
> messages when replication can't succeed because a message size is too large.
> Logging an error here would allow users that get into a bad state to find out
> why it is happening more easily. (Consumers should already be logging a
> useful error message.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
