You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Bankim Bhavsar (Jira)" <ji...@apache.org> on 2021/07/23 20:28:00 UTC

[jira] [Updated] (KUDU-3308) Add health check endpoint to Kudu webserver

     [ https://issues.apache.org/jira/browse/KUDU-3308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bankim Bhavsar updated KUDU-3308:
---------------------------------
    Labels: newbie  (was: )

> 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
>            Priority: Major
>              Labels: newbie
>
> 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 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 /.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)