Christo Lolov created KAFKA-16790:
-------------------------------------
Summary: Calls to RemoteLogManager are made before it is configured
Key: KAFKA-16790
URL: https://issues.apache.org/jira/browse/KAFKA-16790
Project: Kafka
Issue Type: Bug
Components: kraft
Affects Versions: 3.8.0
Reporter: Christo Lolov
BrokerMetadataPublisher#onMetadataUpdate calls ReplicaManager#applyDelta (1)
which in turn calls RemoteLogManager#onLeadershipChange (2), however, the
RemoteLogManager is configured after the BrokerMetadataPublisher starts running
(3, 4). This is incorrect, we either need to initialise the RemoteLogManager
before we start the BrokerMetadataPublisher or we need to skip calls to
onLeadershipChange if the RemoteLogManager is not initialised.
(1)
[https://github.com/apache/kafka/blob/trunk/core/src/main/scala/kafka/server/metadata/BrokerMetadataPublisher.scala#L151]
(2)
[https://github.com/apache/kafka/blob/trunk/core/src/main/scala/kafka/server/ReplicaManager.scala#L2737]
(3)
[https://github.com/apache/kafka/blob/trunk/core/src/main/scala/kafka/server/BrokerServer.scala#L432]
(4)
[https://github.com/apache/kafka/blob/trunk/core/src/main/scala/kafka/server/BrokerServer.scala#L515]
The way to reproduce the problem is by looking at the following branch <TODO>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)