[
https://issues.apache.org/jira/browse/KAFKA-3737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15329482#comment-15329482
]
Florian Hussonnois commented on KAFKA-3737:
-------------------------------------------
Hi Gwen,
My concern is more about the kafka.common.MessageSizeTooLargeException which is
logged with the INFO level.
Actually, I think most of users are collecting error messages based on log
level in order to detect anomalies in a production environment.
I don't know if property "max.message.bytes" is controlled on client side or on
broker side.
If this property is controlled on broker side it could be more convenient to
control it before sending from client ?
This would allow to not overload brokers in case of too heavy messages.
Moreover, this could improve security producers will not be allowed to send
very big messages.
Thanks,
> Closing connection during produce request should be log with WARN level.
> ------------------------------------------------------------------------
>
> Key: KAFKA-3737
> URL: https://issues.apache.org/jira/browse/KAFKA-3737
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.9.0.1
> Reporter: Florian Hussonnois
> Priority: Trivial
>
> Currently if an an error occurred during a produce request the exeception is
> log as info.
> INFO [KafkaApi-0] Closing connection due to error during produce request with
> correlation id 24 from client id console-producer with ack=0
> Topic and partition to exceptions: [test,0] ->
> kafka.common.MessageSizeTooLargeException (kafka.server.KafkaApis)
> It could be more conveniant to use a WARN level to ease the tracing of this
> errors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
