[
https://issues.apache.org/jira/browse/KAFKA-20055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
黃竣陽 reassigned KAFKA-20055:
---------------------------
Assignee: 黃竣陽 (was: Chia-Ping Tsai)
> Ensure BrokerMetadataPublisher applies dynamic configurations before
> initializing managers
> ------------------------------------------------------------------------------------------
>
> Key: KAFKA-20055
> URL: https://issues.apache.org/jira/browse/KAFKA-20055
> Project: Kafka
> Issue Type: Bug
> Reporter: Chia-Ping Tsai
> Assignee: 黃竣陽
> Priority: Major
>
> from [https://github.com/apache/kafka/pull/20334#discussion_r2654901014]
>
> Currently, in {{{}BrokerMetadataPublisher{}}}, the method
> {{initializeManagers()}} is invoked before
> {{{}dynamicConfigPublisher.onMetadataUpdate(delta, newImage){}}}.
> This execution order creates a window where components initialized within
> {{initializeManagers}} (such as the {{{}LogManager{}}}) do not have access to
> the latest broker-level or cluster-level dynamic configurations if those
> configs are located at the tail of the metadata log.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
