[ https://issues.apache.org/jira/browse/KAFKA-16539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Arthur updated KAFKA-16539: --------------------------------- Description: In migration mode, ZK brokers will have a forwarding manager configured. This is used to forward requests to the KRaft controller once we get to that part of the migration. However, prior to KRaft taking over as the controller (known as pre-migration mode), the ZK brokers are still attempting to forward IncrementalAlterConfigs to the controller. This works fine for cluster level configs (e.g., "{{--entity-type broker --entity-default}}"), but this fails for specific broker configs (e.g., "{{--entity-type broker --entity-id 1}}"). This affects BROKER and BROKER_LOGGER config types. To workaround this bug, you can either disable migrations on the brokers (assuming no migration has taken place), or proceed with the migration and get to the point where KRaft is the controller. was: In migration mode, ZK brokers will have a forwarding manager configured. This is used to forward requests to the KRaft controller once we get to that part of the migration. However, prior to KRaft taking over as the controller (known as pre-migration mode), the ZK brokers are still attempting to forward IncrementalAlterConfigs to the controller. This works fine for cluster level configs (e.g., "--entity-type broker --entity-default"), but this fails for specific broker configs (e.g., "--entity-type broker --entity-id 1"). This affects BROKER and BROKER_LOGGER config types. To workaround this bug, you can either disable migrations on the brokers (assuming no migration has taken place), or proceed with the migration and get to the point where KRaft is the controller. > Can't update specific broker configs in pre-migration mode > ---------------------------------------------------------- > > Key: KAFKA-16539 > URL: https://issues.apache.org/jira/browse/KAFKA-16539 > Project: Kafka > Issue Type: Bug > Components: config, kraft > Affects Versions: 3.6.0, 3.7.0, 3.6.1, 3.6.2 > Reporter: David Arthur > Assignee: David Arthur > Priority: Major > Fix For: 3.8.0, 3.7.1, 3.6.3 > > > In migration mode, ZK brokers will have a forwarding manager configured. This > is used to forward requests to the KRaft controller once we get to that part > of the migration. However, prior to KRaft taking over as the controller > (known as pre-migration mode), the ZK brokers are still attempting to forward > IncrementalAlterConfigs to the controller. > This works fine for cluster level configs (e.g., "{{--entity-type broker > --entity-default}}"), but this fails for specific broker configs (e.g., > "{{--entity-type broker --entity-id 1}}"). > This affects BROKER and BROKER_LOGGER config types. > To workaround this bug, you can either disable migrations on the brokers > (assuming no migration has taken place), or proceed with the migration and > get to the point where KRaft is the controller. -- This message was sent by Atlassian Jira (v8.20.10#820010)