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

Posted to jira@kafka.apache.org by "Divij Vaidya (Jira)" <ji...@apache.org> on 2023/05/30 14:31:00 UTC

[jira] [Commented] (KAFKA-15039) Reduce logging level to trace in PartitionChangeBuilder.tryElection()

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

Divij Vaidya commented on KAFKA-15039:
--------------------------------------

Thank you for the find. Could you please share the CPU profile and attach it to this ticket? It would be interesting to compare it with non-kraft profiles such as captured in https://issues.apache.org/jira/browse/KAFKA-14633 

> Reduce logging level to trace in PartitionChangeBuilder.tryElection()
> ---------------------------------------------------------------------
>
>                 Key: KAFKA-15039
>                 URL: https://issues.apache.org/jira/browse/KAFKA-15039
>             Project: Kafka
>          Issue Type: Improvement
>          Components: kraft
>            Reporter: Ron Dagostino
>            Assignee: Ron Dagostino
>            Priority: Major
>             Fix For: 3.6.0
>
>
> A CPU profile in a large cluster showed PartitionChangeBuilder.tryElection() taking significant CPU due to logging.  Decrease the logging statements in that method from debug level to trace to mitigate the impact of this CPU hog under normal operations.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)