[ 
https://issues.apache.org/jira/browse/KUDU-3308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17435720#comment-17435720
 ] 

ASF subversion and git services commented on KUDU-3308:
-------------------------------------------------------

Commit b4da33b6c4df8eb8137cbf7663982822260ee301 in kudu's branch 
refs/heads/master from Zoltan Chovan
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=b4da33b ]

KUDU-3308: Add health check endpoint to webserver

[server] This change adds a '/healthz' endpoint to the kudu-master and
tablet-server webinterfaces.
This endpoint only returns the HTTPStatus 200 and an 'OK' message, for
liveliness probe usage. As the Webserver only starts after the RPC
Server has been started there is no need to add an initial wait time for
the first check.

Change-Id: Ic735e210d95aeec1dfd1335ee972318f12d52475
Reviewed-on: http://gerrit.cloudera.org:8080/17962
Tested-by: Kudu Jenkins
Reviewed-by: Alexey Serbin <aser...@cloudera.com>
Reviewed-by: Bankim Bhavsar <ban...@cloudera.com>


> 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
>
> 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)

Reply via email to