You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "David Arthur (Jira)" <ji...@apache.org> on 2022/08/03 18:30:00 UTC

[jira] [Created] (KAFKA-14136) AlterConfigs in KRaft does not generate records for unchanged values

David Arthur created KAFKA-14136:
------------------------------------

             Summary: 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
            Reporter: David Arthur
            Assignee: David Arthur
             Fix For: 3.3.0, 3.4.0


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)