jyothsnapk17 commented on a change in pull request #4835: [AIRFLOW-XXXX]
Improvements to formatted content in documentation
URL: https://github.com/apache/airflow/pull/4835#discussion_r262627573
##########
File path: docs/howto/check-health.rst
##########
@@ -33,15 +33,17 @@ To check the health status of your Airflow instance, you
can simply access the e
}
}
-* The ``status`` of each component can be either "healthy" or "unhealthy".
-
- * The status of ``metadatabase`` is depending on whether a valid
connection can be initiated
- with the database backend of Airflow.
- * The status of ``scheduler`` is depending on when the latest scheduler
heartbeat happened. If the latest
- scheduler heartbeat happened 30 seconds (default value) earlier than the
current time, scheduler component is
- considered unhealthy. You can also specify this threshold value by
changing
- ``scheduler_health_check_threshold`` in ``scheduler`` section of the
``airflow.cfg`` file.
-
-* The response code of ``"/health"`` endpoint is not used to label the health
status of the
- application (it would always be 200). Hence please be reminded not to use
the response code here
- for health-check purpose.
+* The ``status`` of each component can be either "healthy" or "unhealthy"
+
+ * The status of ``metadatabase`` depends on whether a valid connection can
be initiated with the database
+
+ * The status of ``scheduler`` depends on when the latest scheduler heartbeat
was received
+
+ * If the last heartbeat was received more than 30 seconds (default value)
earlier than the current time, the scheduler is
+ considered unhealthy
+ * This threshold value can be specified using the option
``scheduler_health_check_threshold`` within the
+ ``scheduler`` section in ``airflow.cfg``
+
+Please keep in mind that the HTTP response code of ``"/health"`` endpoint
**should not** be used to determine the health
Review comment:
my bad, missed the first set of quotes. :)
----------------------------------------------------------------
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:
[email protected]
With regards,
Apache Git Services
