[ https://issues.apache.org/jira/browse/KAFKA-16126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17824828#comment-17824828 ]
Divij Vaidya commented on KAFKA-16126: -------------------------------------- Seems like the associated commit in the PR was merged to 3.6, 3.7 and trunk. 3.6 -[https://github.com/apache/kafka/commit/b743f6fd884132c7a5c4e9d96ed62e3aec29007f] 3.7 - [https://github.com/apache/kafka/commit/b40368330814888d7f7f2fda3f5b7ecfa1eabeb2] trunk - [https://github.com/apache/kafka/commit/0015d0f01b130992acc37da85da6ee2088186a1f] I am correcting the fix version here and closing this ticket. > Kcontroller dynamic configurations may fail to apply at startup > --------------------------------------------------------------- > > Key: KAFKA-16126 > URL: https://issues.apache.org/jira/browse/KAFKA-16126 > Project: Kafka > Issue Type: Bug > Affects Versions: 3.7.0 > Reporter: Colin McCabe > Assignee: Colin McCabe > Priority: Blocker > > Some kcontroller dynamic configurations may fail to apply at startup. This > happens because there is a race between registering the reconfigurables to > the DynamicBrokerConfig class, and receiving the first update from the > metadata publisher. We can fix this by registering the reconfigurables first. > This seems to have been introduced by the "MINOR: Install ControllerServer > metadata publishers sooner" change. -- This message was sent by Atlassian Jira (v8.20.10#820010)