layoaster opened a new issue, #15546: URL: https://github.com/apache/druid/issues/15546
### Affected Version Druid 27.0.0 ### Description I run Druid on a Kubernetes cluster and found out that when restarting a Historical node (rolling upgrades) the liveness probes do not respond until the Historical has fully loaded all the segments on the cache (k8s Persistent Volume). Loading the segments from the cache (disk) takes more than 5 min in my cluster because there are more than 28k segments per historical. I believe the liveness probe [`/status/health`](https://druid.apache.org/docs/latest/api-reference/service-status-api#get-service-health) should respond with a 200 as soon as the process is up an reachable (network) regardless of its initialization status. Reporting on how long it takes to initialize and load segments from the cache and deep storage is the purpose of the readiness probe `/druid/historical/v1/readiness`. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
