[jira] [Updated] (KAFKA-16126) Kcontroller dynamic configurations may fail to apply at startup

2024-03-08 Thread Divij Vaidya (Jira)


 [ 
https://issues.apache.org/jira/browse/KAFKA-16126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Divij Vaidya updated KAFKA-16126:
-
Component/s: kraft

> 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
>  Components: kraft
>Affects Versions: 3.7.0
>Reporter: Colin McCabe
>Assignee: Colin McCabe
>Priority: Blocker
> Fix For: 3.7.0, 3.6.2
>
>
> 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)


[jira] [Updated] (KAFKA-16126) Kcontroller dynamic configurations may fail to apply at startup

2024-03-08 Thread Divij Vaidya (Jira)


 [ 
https://issues.apache.org/jira/browse/KAFKA-16126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Divij Vaidya updated KAFKA-16126:
-
Fix Version/s: (was: 3.8.0)

> 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
> Fix For: 3.7.0, 3.6.2
>
>
> 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)


[jira] [Updated] (KAFKA-16126) Kcontroller dynamic configurations may fail to apply at startup

2024-03-08 Thread Divij Vaidya (Jira)


 [ 
https://issues.apache.org/jira/browse/KAFKA-16126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Divij Vaidya updated KAFKA-16126:
-
Fix Version/s: 3.6.2
   3.8.0
   3.7.0

> 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
> Fix For: 3.7.0, 3.6.2, 3.8.0
>
>
> 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)