[
https://issues.apache.org/jira/browse/KAFKA-19117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17943842#comment-17943842
]
Siddhartha Devineni edited comment on KAFKA-19117 at 4/13/25 1:45 PM:
----------------------------------------------------------------------
Hello [~rkalasapur],
I have changed the log level to warn in the NetworkClient as follows:
https://github.com/apache/kafka/pull/19456
Please have a look.
Thank you
was (Author: JIRAUSER309328):
Hello [~rkalasapur],
Could I take up this task?
Thank you
> Client Throttling Log messages should be of log level - WARN (Java client)
> --------------------------------------------------------------------------
>
> Key: KAFKA-19117
> URL: https://issues.apache.org/jira/browse/KAFKA-19117
> Project: Kafka
> Issue Type: Improvement
> Components: clients, logging
> Affects Versions: 3.6.2
> Reporter: Ravi Kalasapur
> Priority: Minor
>
> We experienced an outage in our application due to a built up Kafka lag,
> which we eventually discovered to be the problem with Kafka Clients being
> throttled.
> Even when using the confluent cluster, the dashboard does point to exceeding
> the quota of the principal.
> It will be nice, if the log message on the client side is a WARNING. This
> helps those who don't have visibility to cluster, and just look at the
> problem from the client side, setup alerts etc. (instead of enabling TRACE to
> figure out where the problem is)
>
> NetworkClient#maybeThrottle
> {code:java}
> log.trace("Connection to node {} is throttled for {} ms until timestamp {}",
> nodeId, throttleTimeMs, now + throttleTimeMs); {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
