dschneiderch commented on issue #14261:
URL: https://github.com/apache/airflow/issues/14261#issuecomment-1284289128
hi, I am still running into this behavior. Using the provided Airflow 2.3.4
image with Helm chart 1.7 and the scheduler restarts every 5 min. I logged into
the scheduler pod and ran the liveness probe as listed in teh config
```airflow@bairflow-scheduler-0:/opt/airflow$ sh -c
"CONNECTION_CHECK_MAX_COUNT=0 AIRFLOW__LOGGING__LOGGING_LEVEL=ERROR exec
/entrypoint \
airflow jobs check --job-type SchedulerJob --hostname
$(hostname)"
No alive jobs found.
airflow@bairflow-scheduler-0:/opt/airflow$ echo $?
1```
and it always returns exit code 1. based on
https://airflow.apache.org/docs/apache-airflow/stable/logging-monitoring/check-health.html#scheduler-health-check-server
we switched the livenessprobe command to ```scheduler:
livenessProbe:
command: ["bash", "-c", "airflow jobs check --job-type SchedulerJob
--allow-multiple --limit 100"]
``` and it returns 0 and appears the solve the issue.
--
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]
