[
https://issues.apache.org/jira/browse/KAFKA-5057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15967819#comment-15967819
]
Gwen Shapira commented on KAFKA-5057:
-------------------------------------
I thought of a new configuration (which made me realize this will require a
KIP).
Basically, sometimes users bump up max.request.size, but only expect very few
large messages (since large messages have impact on garbage collection,
throughput, etc). Such log will let them track the number of large messages,
their size and their source so they can see if their expectation is correct and
adjust course if it isn't. So I will set max.request.size to 10MB, but the
logging threshold to 1MB, because I expect very few messages between 1MB and
10MB.
Does that make sense?
> "Big Message Log"
> -----------------
>
> Key: KAFKA-5057
> URL: https://issues.apache.org/jira/browse/KAFKA-5057
> Project: Kafka
> Issue Type: Bug
> Reporter: Gwen Shapira
>
> Really large requests can cause significant GC pauses which can cause quite a
> few other symptoms on a broker. Will be nice to be able to catch them.
> Lets add the option to log details (client id, topic, partition) for every
> produce request that is larger than a configurable threshold.
> /cc [~apurva]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
