[jira] [Resolved] (KAFKA-10469) Respect logging hierarchy (KIP-676)

["Ismael Juma (Jira)" <ji...@apache.org>]

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

Ismael Juma resolved KAFKA-10469.
---------------------------------
    Fix Version/s: 2.8.0
       Resolution: Fixed

> Respect logging hierarchy (KIP-676)
> -----------------------------------
>
>                 Key: KAFKA-10469
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10469
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>            Reporter: Tom Bentley
>            Assignee: Tom Bentley
>            Priority: Major
>             Fix For: 2.8.0
>
>
> {{Log4jController#loggers}} incorrectly uses the root logger's log level for any loggers which lack a configured log level of their own. This is incorrect because loggers without an explicit level inherit their level from their parent logger and this resolved level might be different from the root logger's level. This means that the levels reported from {{Admin.describeConfigs}}, which uses {{Log4jController#loggers}} are incorrect. This can be shown by using the default {{log4j.properties}} and describing a broker's loggers, it reports
> {noformat}
> kafka.controller=TRACE
> kafka.controller.ControllerChannelManager=INFO
> kafka.controller.ControllerEventManager$ControllerEventThread=INFO
> kafka.controller.KafkaController=INFO
> kafka.controller.RequestSendThread=INFO
> kafka.controller.TopicDeletionManager=INFO
> kafka.controller.ZkPartitionStateMachine=INFO
> kafka.controller.ZkReplicaStateMachine=INFO
> {noformat}
> The default {{log4j.properties}} does indeed set {{kafka.controller}} to {{TRACE}}, but it does not configure the others, so they're actually at {{TRACE}} not {{INFO}} as reported.



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