[
https://issues.apache.org/jira/browse/KUDU-3308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Serbin resolved KUDU-3308.
---------------------------------
Fix Version/s: 1.16.0
Resolution: Fixed
> Add health check endpoint to Kudu webserver
> -------------------------------------------
>
> Key: KUDU-3308
> URL: https://issues.apache.org/jira/browse/KUDU-3308
> Project: Kudu
> Issue Type: Improvement
> Components: server
> Reporter: Bankim Bhavsar
> Assignee: Zoltan Chovan
> Priority: Major
> Labels: newbie
> Fix For: 1.16.0
>
>
> For integrating with Kubernetes, it'd be good to add a webserver endpoint
> (/healthz) that exposes health of the kudu cluster.
> We need something that's very lightweight that responds back quickly with
> simply HTTP status code. This endpoint is expected to be queried every 5-10
> secs. If required, we can add a query parameter that'll return back more
> detailed information.
> The idea is to use this with livenessProbe/readinessProbe/startupProbe in
> Kubernetes.
>
> [https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/]
> As a workaround, currently we can use the base landing page /.
> Alternatively we could think about introducing a lightweight ksck.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
