You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Rishika Modi (Jira)" <ji...@apache.org> on 2020/09/05 12:57:00 UTC
[jira] [Commented] (KAFKA-9795) Add throttleTimeMs in logs
[ https://issues.apache.org/jira/browse/KAFKA-9795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17191049#comment-17191049 ]
Rishika Modi commented on KAFKA-9795:
-------------------------------------
[~vavr] Shall I pick up this ?
> Add throttleTimeMs in logs
> --------------------------
>
> Key: KAFKA-9795
> URL: https://issues.apache.org/jira/browse/KAFKA-9795
> Project: Kafka
> Issue Type: Improvement
> Components: log, logging
> Reporter: Igor Vavrzhin
> Priority: Minor
>
> if trotting is triggered on a broker, then the client receives something like this:
> {code:java}
> org.apache.kafka.clients.FetchSessionHandler.handleResponse
> FetchResponse
> throttleTimeMs = 2583
> error = {Errors} "NONE"
> sessionId = 0
> responseData = {LinkedHashMap} size = 0 {code}
> which in the logs looks like:
> {code:java}
> [INFO ] o.a.k.c.FetchSessionHandler [Consumer clientId=dev, groupId=null] Node 18 sent an invalid full fetch response with extra=(topicName-11, response=( {code}
> It would be great to see the reason and parameter *throttleTimeMs* in the logs!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)