[jira] [Commented] (KAFKA-13625) KIP-817: Fix inconsistency in dynamic application log levels

["Dongjin Lee (Jira)" <ji...@apache.org>]

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

Dongjin Lee commented on KAFKA-13625:
-------------------------------------

This issue is a derivative issue of KAFKA-7800; Found while working on KAFKA-9366.

> KIP-817: Fix inconsistency in dynamic application log levels
> ------------------------------------------------------------
>
>                 Key: KAFKA-13625
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13625
>             Project: Kafka
>          Issue Type: Improvement
>          Components: core
>            Reporter: Dongjin Lee
>            Assignee: Dongjin Lee
>            Priority: Minor
>
> As of present, there are two ways of changing log levels in Runtime:
>  # JMX API
>  # Admin API
> However, there are some inconsistencies between these two ways;
>  # JMX API allows OFF level; but Admin API does not. If the user tries to set the logger's level to OFF, Kafka responds with INVALID_CONFIG (40) error.
>  # JMX API converts unsupported log level to DEBUG; but Admin API throws an error. The documentation does not state this difference in semantics.
> To fix these inconsistencies, we have to:
>  # Add OFF level to LogLevelConfig.
>  # Add documentation on different semantics between JMX and Admin API.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)