[
https://issues.apache.org/jira/browse/KAFKA-14136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur updated KAFKA-14136:
---------------------------------
Component/s: kraft
> AlterConfigs in KRaft does not generate records for unchanged values
> --------------------------------------------------------------------
>
> Key: KAFKA-14136
> URL: https://issues.apache.org/jira/browse/KAFKA-14136
> Project: Kafka
> Issue Type: Bug
> Components: kraft
> Reporter: David Arthur
> Assignee: David Arthur
> Priority: Major
> Fix For: 3.3.0, 3.4.0, 3.2.2
>
>
> In ZK, when handling LegacyAlterConfigs or IncrementalAlterConfigs, we call
> certain code paths regardless of what values are included in the request. We
> utilize this behavior to force a broker to reload a keystore or truststore
> from disk (we sent an AlterConfig with the keystore path unchanged).
> In KRaft, however, we have an optimization to only generate ConfigRecords if
> the incoming AtlerConfig request will result in actual config changes. This
> means the broker never receives any records for "no-op" config changes and we
> cannot trigger certain code paths.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
