You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Chia-Ping Tsai (Jira)" <ji...@apache.org> on 2025/12/16 04:30:00 UTC

[jira] [Updated] (KAFKA-19997) Improve handling and visibility of invalid dynamic configurations

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

Chia-Ping Tsai updated KAFKA-19997:
-----------------------------------
    Description: 
from: https://github.com/apache/kafka/pull/20334#discussion_r2621722784

Warning messages for invalid dynamic configurations are easily overlooked and difficult to monitor. Therefore, I propose two improvements: 

1) introduce a new configuration, "dynamic.config.failure.policy ", to allow users to halt the server upon validation failure if desired 

2) add a new metric, `InvalidConfigCount`, to expose the invalid configurations via JMX 

  was:
Warning messages for invalid dynamic configurations are easily overlooked and difficult to monitor. Therefore, I propose two improvements: 

1) introduce a new configuration, "dynamic.config.failure.policy ", to allow users to halt the server upon validation failure if desired 

2) add a new metric, `InvalidConfigCount`, to expose the invalid configurations via JMX 


> Improve handling and visibility of invalid dynamic configurations
> -----------------------------------------------------------------
>
>                 Key: KAFKA-19997
>                 URL: https://issues.apache.org/jira/browse/KAFKA-19997
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Chia-Ping Tsai
>            Assignee: Chia-Ping Tsai
>            Priority: Major
>
> from: https://github.com/apache/kafka/pull/20334#discussion_r2621722784
> Warning messages for invalid dynamic configurations are easily overlooked and difficult to monitor. Therefore, I propose two improvements: 
> 1) introduce a new configuration, "dynamic.config.failure.policy ", to allow users to halt the server upon validation failure if desired 
> 2) add a new metric, `InvalidConfigCount`, to expose the invalid configurations via JMX 



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