rcheatham-q commented on issue #31200: URL: https://github.com/apache/airflow/issues/31200#issuecomment-1545841662
I can confirm that the default liveness probe for the scheduler is failing. The helm chart v1.9.0 defines the liveness probe as follows: ``` CONNECTION_CHECK_MAX_COUNT=0 AIRFLOW__LOGGING__LOGGING_LEVEL=ERROR exec /entrypoint airflow jobs check --job-type SchedulerJob --local ``` However, executing that command on a live and functioning scheduler pod fails (I omitted the `exec` command so I could check the exit code): ``` airflow@airflow-scheduler-866db5c895-qt5pq:/opt/airflow$ CONNECTION_CHECK_MAX_COUNT=0 AIRFLOW__LOGGING__LOGGING_LEVEL=ERROR /entrypoint airflow jobs check --job-type SchedulerJob --local No alive jobs found. airflow@airflow-scheduler-866db5c895-qt5pq:/opt/airflow$ echo $? 1 airflow@airflow-scheduler-866db5c895-qt5pq:/opt/airflow$ ``` I can confirm that the liveness check listed by @ptran32 does function, however it does not seem to directly detect if the scheduler job is running. I also tested the example `airflow jobs check` commands listed in [the CLI docs](https://airflow.apache.org/docs/apache-airflow/2.6.0/cli-and-env-variables-ref.html#check_repeat1) and both functioned the same. It appears that the scheduler healthchecks in general are broken in version 2.6.0. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
