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

Posted to jira@kafka.apache.org by "Colin McCabe (Jira)" <ji...@apache.org> on 2020/03/04 19:30:00 UTC

[jira] [Assigned] (KAFKA-9625) Unable to Describe broker configurations that have been set via IncrementalAlterConfigs

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

Colin McCabe reassigned KAFKA-9625:
-----------------------------------

    Assignee: Sanjana Kaundinya  (was: Colin McCabe)

> Unable to Describe broker configurations that have been set via IncrementalAlterConfigs
> ---------------------------------------------------------------------------------------
>
>                 Key: KAFKA-9625
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9625
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>            Reporter: Colin McCabe
>            Assignee: Sanjana Kaundinya
>            Priority: Critical
>             Fix For: 2.6.0
>
>
> There seem to be at least two bugs in the broker configuration APIs and/or logic:
> 1. Broker throttles are incorrectly marked as sensitive configurations.  This includes leader.replication.throttled.rate, follower.replication.throttled.rate, replica.alter.log.dirs.io.max.bytes.per.second.  This means that their values cannot be read back by DescribeConfigs after they are set.
> 2. When we clear the broker throttles via incrementalAlterConfigs, DescribeConfigs continues returning the old throttles indefinitely.  In other words, the clearing is not reflected in the Describe API.



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