You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A backfill launched from the scheduler pod, queues tasks as it should but while they are in the process of starting the kubernentes executor loop running in the scheduler clears these tasks and reschedules them via this function
This causes the backfill to not queue any more tasks and enters an endless loop of waiting for the task it has queued to complete.
The way I have mitigated this is to set the AIRFLOW__KUBERNETES__WORKER_PODS_QUEUED_CHECK_INTERVAL to 3600, which is not ideal
What you think should happen instead
The function clear_not_launched_queued_tasks should respect tasks launched by a backfill process and not clear them.
How to reproduce
start a backfill with large number of tasks and watch as they get queued and then subsequently rescheduled by the kubernetes executor running in the scheduler pod
i think, we need to add a filter TaskInstance.queued_by_job_id == self.job_id. so that the schedulerJob does not clear backfilljob's taskinstnace and vice versa.
Apache Airflow version
2.2.5 (latest released)
What happened
A backfill launched from the scheduler pod, queues tasks as it should but while they are in the process of starting the kubernentes executor loop running in the scheduler clears these tasks and reschedules them via this function
airflow/airflow/executors/kubernetes_executor.py
Line 444 in 9449a10
This causes the backfill to not queue any more tasks and enters an endless loop of waiting for the task it has queued to complete.
The way I have mitigated this is to set the
AIRFLOW__KUBERNETES__WORKER_PODS_QUEUED_CHECK_INTERVAL
to 3600, which is not idealWhat you think should happen instead
The function clear_not_launched_queued_tasks should respect tasks launched by a backfill process and not clear them.
How to reproduce
start a backfill with large number of tasks and watch as they get queued and then subsequently rescheduled by the kubernetes executor running in the scheduler pod
Operating System
Debian GNU/Linux 10 (buster)
Versions of Apache Airflow Providers
Deployment
Other 3rd-party Helm chart
Deployment details
Deployment is running the latest helm chart of Airflow Community Edition
Anything else
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: