[
https://issues.apache.org/jira/browse/KAFKA-9625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17062924#comment-17062924
]
ASF GitHub Bot commented on KAFKA-9625:
---------------------------------------
cmccabe commented on pull request #8206: KAFKA-9625: Broker throttles are
incorrectly marked as sensitive configurations
URL: https://github.com/apache/kafka/pull/8206
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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)
