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

Posted to commits@airflow.apache.org by "jack (JIRA)" <ji...@apache.org> on 2019/02/11 10:05:00 UTC

[jira] [Commented] (AIRFLOW-2971) Health check command for scheduler

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

jack commented on AIRFLOW-2971:
-------------------------------

[~XD-DENG] didn't your PR [https://github.com/apache/airflow/pull/4309] fixed this?

> Health check command for scheduler
> ----------------------------------
>
>                 Key: AIRFLOW-2971
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-2971
>             Project: Apache Airflow
>          Issue Type: Bug
>            Reporter: Jon Davies
>            Priority: Major
>
> As part of a Kubernetes deployment of Airflow, I would like to define an exec command based health check for the Airflow scheduler:
> - https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/
> ...the webserver is simple as all that needs is checking that the HTTP port is available. For the scheduler, it would be neat to have a command such as:
> airflow scheduler health
> That returned OK and exit 0/NOT OK and a non-zero value when it cannot reach the database for instance.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)