You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Umesh Chaudhary (JIRA)" <ji...@apache.org> on 2017/04/12 09:39:42 UTC

[jira] [Commented] (KAFKA-5057) "Big Message Log"

    [ https://issues.apache.org/jira/browse/KAFKA-5057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15965615#comment-15965615 ] 

Umesh Chaudhary commented on KAFKA-5057:
----------------------------------------

[~gwenshap] currently we have "max.request.size" configuration for a producer, do you suggest to print the log message based on this config or to introduce a new config to define the threshold? 

> "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)