airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nidhi (Jira)" <j...@apache.org>
Subject [jira] [Commented] (AIRFLOW-5506) Airflow scheduler stuck
Date Wed, 11 Dec 2019 21:07:00 GMT

    [ https://issues.apache.org/jira/browse/AIRFLOW-5506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16993899#comment-16993899
] 

Nidhi commented on AIRFLOW-5506:
--------------------------------

I am facing the same issue as I have around 60,000 tasks inside one DAG. When I trigger the
dag it is not scheduling my tasks and DAG is staying into Running state. The DAG stays into
Running state for 2 or 3 days without scheduling the tasks amd in case of Celery workers ,
they are not even receiving the task which I have triggered.

Please let me know if you know how to solve it. I am working with Celery Executor and tried
to change "dagbag_import_timeout" and "max_threads" but nothing is working for my case.

> Airflow scheduler stuck
> -----------------------
>
>                 Key: AIRFLOW-5506
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-5506
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: scheduler
>    Affects Versions: 1.10.4, 1.10.5
>            Reporter: t oo
>            Priority: Major
>
> re-post of [https://stackoverflow.com/questions/57713394/airflow-scheduler-stuck] and
slack discussion
>  
>  
> I'm testing the use of Airflow, and after triggering a (seemingly) large number of DAGs
at the same time, it seems to just fail to schedule anything and starts killing processes.
These are the logs the scheduler prints:
> {{[2019-08-29 11:17:13,542] \{scheduler_job.py:214} WARNING - Killing PID 199809
> [2019-08-29 11:17:13,544] \{scheduler_job.py:214} WARNING - Killing PID 199809
> [2019-08-29 11:17:44,614] \{scheduler_job.py:214} WARNING - Killing PID 2992
> [2019-08-29 11:17:44,614] \{scheduler_job.py:214} WARNING - Killing PID 2992
> [2019-08-29 11:18:15,692] \{scheduler_job.py:214} WARNING - Killing PID 5174
> [2019-08-29 11:18:15,693] \{scheduler_job.py:214} WARNING - Killing PID 5174
> [2019-08-29 11:18:46,765] \{scheduler_job.py:214} WARNING - Killing PID 22410
> [2019-08-29 11:18:46,766] \{scheduler_job.py:214} WARNING - Killing PID 22410
> [2019-08-29 11:19:17,845] \{scheduler_job.py:214} WARNING - Killing PID 42177
> [2019-08-29 11:19:17,846] \{scheduler_job.py:214} WARNING - Killing PID 42177
> ...}}
> I'm using a LocalExecutor with a PostgreSQL backend DB. It seems to be happening only
after I'm triggering a large number (>100) of DAGs at about the same time using external
triggering. As in:
> {{airflow trigger_dag DAG_NAME}}
> After waiting for it to finish killing whatever processes he is killing, he starts executing
all of the tasks properly. I don't even know what these processes were, as I can't really
see them after they are killed...
> Did anyone encounter this kind of behavior? Any idea why would that happen?
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message