[KAFKA-13835] Fix two bugs related to dynamic broker configs in KRaft

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 3.2.0
• Assignee: Colin McCabe
• Reporter: Colin McCabe
• Created: 18/Apr/22 21:54
• Updated: 12/Nov/24 03:04
• Resolved: 12/Nov/24 03:04

Description

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.

Issue Links

• links to: GitHub Pull Request #12063