[ https://issues.apache.org/jira/browse/AIRFLOW-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16766731#comment-16766731
]
Xiaodong DENG commented on AIRFLOW-2971:
----------------------------------------
Thanks [~jackjack10]. Yes I think so.
But we need to note that my PR 4309 provided an API endpoint to do the health check, rather
than a command. Personally I believe an API endpoint makes more sense than a command does
in this scenario.
> 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)
|