You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/01/16 17:33: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=17017330#comment-17017330 ] 

ASF GitHub Bot commented on AIRFLOW-2971:
-----------------------------------------

stale[bot] commented on pull request #6277: [AIRFLOW-2971] Add health check CLI for scheduler
URL: https://github.com/apache/airflow/pull/6277
 
 
   
 
----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Health check command for scheduler
> ----------------------------------
>
>                 Key: AIRFLOW-2971
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-2971
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: scheduler
>            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
(v8.3.4#803005)