pjain1 commented on issue #15546: URL: https://github.com/apache/druid/issues/15546#issuecomment-1900722341
@layoaster I think there is some confusion here. You don't need to adjust thresholds etc. if you have a `startupProbe` with `/druid/historical/v1/readiness`, then k8s will only start using liveness probe when startupProbe at `/druid/historical/v1/readiness` succeeds. This endpoint returns OK only after all segments are loaded from the local cache and it is ready to serve the queries. Historicals also announces itself to brokers only after this. So you can use liveness probe at `/status/health` with normal thresholds. I hope its clear now. You just need to adjust startup probe thresholds as per your historical start times, will depend on how much data is loaded on it. Startup probe is created for this purpose only, read here - https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#define-startup-probes -- 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]
