jiafu1115 commented on PR #20007: URL: https://github.com/apache/kafka/pull/20007#issuecomment-3027094794
@kamalcph thanks for comments When restarting broker. The connection to query/create topic in "TopicBasedRemoteLogMetadataManager#initializeResources"will fail until the broker's self get ready. [2025-06-03 23:21:20,752] WARN [AdminClient clientId=adminclient-1] Connection to node -1 ([10.20.1.125:9559)](https://10-20-1-125/) could not be established. Node may not be available. [2025-06-03 23:21:21,282] INFO [BrokerServer id=2] Transition from STARTING to STARTED (kafka.server.BrokerServer) the node 10.20.1.125:9559 is the server self due to the configure: "advertised.listeners": "INTERNAL_SSL://10.20.1.125:9559", remote.log.metadata.manager.listener.name:INTERNAL_SSL So. the configure is using the local host as the first request to get metadata. right? So it won't success connected to itself. Thus it is restarting. Besides this. even we configure the endpoint to some other kafka cluster's endpoint or some other endpoints. We still have one case which we will restart all the server at the same time. That will also cause we can't make sure the connection is always success. What's more. initializeResources is not only check the topic existed. it also check some other items: (1) time.milliseconds() - startTimeMs > rlmmConfig.initializationRetryMaxTimeoutMs() (2) if (!isPartitionsCountSameAsConfigured(adminClient, topicName)) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
