fantapsody commented on issue #9201: URL: https://github.com/apache/pulsar/issues/9201#issuecomment-1208840922
@heesung-sn During the container start K8s will access the `/status.html` API periodically to check if the broker is fully started, and the broker is considered to be started when [`PulsarService.start` finishes](https://github.com/apache/pulsar/blob/master/pulsar-broker/src/main/java/org/apache/pulsar/broker/PulsarService.java#L894). Before started, the status API will just throw not found exception: https://github.com/apache/pulsar/blob/master/pulsar-broker-common/src/main/java/org/apache/pulsar/common/configuration/VipStatus.java#L57 . So it should have no actual harm to the pulsar cluster. Maybe we can improve the status API to write some log like `Pulsar service is not ready` rather than throwing an exception directly. -- 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]
