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

Posted to jira@kafka.apache.org by "Jun Rao (Jira)" <ji...@apache.org> on 2020/03/26 21:56:00 UTC

[jira] [Resolved] (KAFKA-8470) State change logs should not be in TRACE level

     [ https://issues.apache.org/jira/browse/KAFKA-8470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jun Rao resolved KAFKA-8470.
----------------------------
    Fix Version/s: 2.6.0
       Resolution: Fixed

Merged the PR to trunk.

    1. Defaults state-change log level to INFO.

    2. INFO level state-change log includes  (a) request level logging with just partition counts; (b) the leader/isr changes per partition in the controller and in the broker (reduced to mostly just 1 logging per partition).

> State change logs should not be in TRACE level
> ----------------------------------------------
>
>                 Key: KAFKA-8470
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8470
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Stanislav Kozlovski
>            Assignee: Stanislav Kozlovski
>            Priority: Minor
>             Fix For: 2.6.0
>
>
> The StateChange logger in Kafka should not be logging its state changes in TRACE level.
> We consider these changes very useful in debugging and we additionally configure that logger to log in TRACE levels by default.
> Since we consider it important enough to configure its own logger to log in a separate log level, why don't we change those logs to INFO and have the logger use the defaults?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)