[
https://issues.apache.org/jira/browse/KAFKA-15137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17741640#comment-17741640
]
Divij Vaidya commented on KAFKA-15137:
--------------------------------------
We are creating a release candidate today as per the plan
[https://cwiki.apache.org/confluence/display/KAFKA/Release+plan+3.5.1]
I am removing the target for 3.5.1 from this JIRA.
> 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.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)
