You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/04/11 11:11:41 UTC

[GitHub] [airflow] mik-laj commented on issue #22895: Airflow health API is returning always 200

mik-laj commented on issue #22895:
URL: https://github.com/apache/airflow/issues/22895#issuecomment-1094920008

   We shouldn't change the code when the scheduler isn't working. This endpoint should only checks health of webserver and required components - metabase. Otherwise the web server will be restarted much more often than necessary.
   
   We have a related note in doc.
   
   > For this check to work, at least one working web server is required. Suppose you use this check for scheduler monitoring, then in case of failure of the web server, you will lose the ability to monitor scheduler, which means that it can be restarted even if it is in good condition. For greater confidence, consider using [CLI Check for Scheduler](https://airflow.apache.org/docs/apache-airflow/stable/logging-monitoring/check-health.html#check-health-cli-checks-for-scheduler).


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

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org