jiafu1115 commented on code in PR #20203:
URL: https://github.com/apache/kafka/pull/20203#discussion_r2462800981
##########
core/src/main/scala/kafka/server/BrokerServer.scala:
##########
@@ -591,6 +600,15 @@ class BrokerServer(
"all of the SocketServer Acceptors to be started",
enableRequestProcessingFuture, startupDeadline, time)
+ brokerReadyCallbacks.foreach { callback =>
+ try {
+ callback.onBrokerReady()
Review Comment:
@chia7712 the key issue is that the initial delay is not fixed value due to
the startup take different time in different kafka cluster. It should >=
startup time to avoid the fail retry when metadata is stored as topic in local
cluster.
cluster A take 10 seconds for startup.the initinal delay should be > 10s
cluster B take 10 minutes for startup. the initinal delay shuld be > 10m
thus. the bad case is that A may incease the startup cost time with
topic/data increased. so you must remeber to change the configure again and
again. or you set one very big value you can make sure the broker never > the
time. That's the workaourd solution I adopt. I set 20m for the configure.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
