cmccabe opened a new pull request, #12063: URL: https://github.com/apache/kafka/pull/12063
The first bug is that we are calling reloadUpdatedFilesWithoutConfigChange when a topic configuration is changed, but not when a broker configuration is changed. This is 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 are related to broker listeners, but which do not involve creating or removing new listeners. We should support these configurations in KRaft. Only adding or removing listeners is unsupported, not changes to existing listeners. This PR fixes the configuration change validation to support this. (This also removes a very puzzling error mesage stating that we are adding or removing listeners, when we are not). -- 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. To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
