[
https://issues.apache.org/jira/browse/KAFKA-3737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15293440#comment-15293440
]
ASF GitHub Bot commented on KAFKA-3737:
---------------------------------------
GitHub user fhussonnois opened a pull request:
https://github.com/apache/kafka/pull/1415
KAFKA-3737: Change log level for error during produce request
Minor change for https://issues.apache.org/jira/browse/KAFKA-3737
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/fhussonnois/kafka kafka-3737
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1415.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1415
----
commit e2dac4a834c84808a8d171dbfdc149f6207e6d4a
Author: Florian Hussonnois <[email protected]>
Date: 2016-05-20T14:24:29Z
KAFKA-3737: Change log level for error during produce request
----
> 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)
