You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Divij Vaidya (Jira)" <ji...@apache.org> on 2023/07/11 09:08:00 UTC
[jira] [Resolved] (KAFKA-15137) Don't log the entire request in KRaftControllerChannelManager
[ https://issues.apache.org/jira/browse/KAFKA-15137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Divij Vaidya resolved KAFKA-15137.
----------------------------------
Resolution: Fixed
> Don't log the entire request in KRaftControllerChannelManager
> -------------------------------------------------------------
>
> Key: KAFKA-15137
> URL: https://issues.apache.org/jira/browse/KAFKA-15137
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 3.5.0, 3.6.0
> Reporter: David Arthur
> Assignee: Alyssa Huang
> Priority: Major
> Fix For: 3.6.0, 3.5.1
>
>
> While debugging some junit tests, I noticed some really long log lines in KRaftControllerChannelManager. When the broker is down, we log a WARN that includes the entire UpdateMetadataRequest or LeaderAndIsrRequest. For large clusters, these can be really large requests, so this could potentially cause excessive output in the log4j logs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)