[
https://issues.apache.org/jira/browse/KAFKA-3737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299191#comment-15299191
]
Gwen Shapira commented on KAFKA-3737:
-------------------------------------
I don't mind bumping up the LOG level, but I don't think this is the log you
were looking for...
This INFO is only when data is sent with "request.required.acks=0" from the
consumer, which theoretically should mean that the producer doesn't care
whether the data made it or not (by the time we write this log, the consumer
already assumes everything is amazing, which is why we need to close the
connector to get its attention).
Maybe the log message you are looking for is:
" debug("Produce request with correlation id %d from client %s on partition %s
failed due to %s".format("
Few lines up?
This is for all the produce errors, but then, this can flood the logs pretty
easily. Brokers handle thousands produce requests per second...
In general:
1. The best way to detect producer errors is from the producer log...
2. We recommend running the broker log at INFO level anyway :)
> 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)
