[jira] [Comment Edited] (KAFKA-13835) Fix two bugs related to dynamic broker configs in KRaft

["Colin McCabe (Jira)" <ji...@apache.org>]

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

Colin McCabe edited comment on KAFKA-13835 at 11/12/24 3:04 AM:
----------------------------------------------------------------

This was merged in Kafka 3.2. I have updated the fix release version and closed it.


was (Author: cmccabe):
This was merged a long time ago, in Kafka 3.2.

> Fix two bugs related to dynamic broker configs in KRaft
> -------------------------------------------------------
>
>                 Key: KAFKA-13835
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13835
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Colin McCabe
>            Assignee: Colin McCabe
>            Priority: Critical
>             Fix For: 3.2.0
>
>
> The first bug is that we were calling reloadUpdatedFilesWithoutConfigChange when a topic configuration was changed, but not when a broker configuration was changed. This was backwards -- this function must be called only for BROKER configs, and never for TOPIC configs. (Also, this function is called only for specific broker configs, not for cluster configs.)
> The second bug is that there were several configurations such as `max.connections` which were related to broker listeners, but which did not involve creating or removing new listeners. We can and should support these configurations in KRaft, since no additional work is needed to support them. Only adding or removing listeners is unsupported. This PR adds support for these by fixing the configuration change validation.



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