GitHub user arkadiuszbach added a comment to the discussion: dagProcessor liveness probe always fails
> Turns out there is a running dagProcessor job in the db but the cli used for > the health check returns no alive jobs `select * from job where > job_type='DagProcessorJob' order by start_date desc;` ` 206 | | running | > DagProcessorJob | 2026-06-26 17:33:29.530223+00 | | 2026-06-26 > 17:37:04.932384+00 | | airflow-dag-processor-5df45489f7-92r7z | airflow` > > `airflow jobs check --job-type DagProcessorJob` `No alive jobs found` > > It seems that maybe the dagProcessor is not sending a heartbeat? > > Guessing this is because the heartbeat is `only_if_necessary` > > [airflow/airflow-core/src/airflow/jobs/dag_processor_job_runner.py](https://github.com/apache/airflow/blob/ba8cfe47e57e101a7b9ec39d4ae4a0b042042862/airflow-core/src/airflow/jobs/dag_processor_job_runner.py#L55) > > Line 55 in > [ba8cfe4](/apache/airflow/commit/ba8cfe47e57e101a7b9ec39d4ae4a0b042042862) > > only_if_necessary=True, > Maybe due to the config option `scheduler.job_heartbeat_sec: 30` Yes its because of `scheduler.job_heartbeat_sec: 30` and `dag_processor.health_check_threshold: 30`, see: https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html#health-check-threshold just increase health_check_threshold for the dag_processor GitHub link: https://github.com/apache/airflow/discussions/69667#discussioncomment-17588038 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
