A reproduction repo for a Scheduling bug in AirFlow 2.2.3

Last update: Feb 09, 2022

Related tags

Overview

How to run

docker-compose build
docker-compose up

Setup

Have 3 DAGs:

~240 Tasks, executes every hour, runs for about 45-50 minutes total
~600 Tasks, executes every 5 days, runs for days
~10 Tasks, executes on trigger, runs for 10-50 minutes

DAGs run on the default_pool with max_active_tasks set to 2.

My AirFlow config file has the following:

parallelism = 32
default_pool_task_slot_count = 6
executor = LocalExecutor
default_task_weight_rule = absolute

parallelism was set initially like that. default_pool_task_slot_count was set to 6, because it seemed rational that if all of my 3 dags are executing at the same time, the maximum amount of tasks that can be executed is 3*2=6.

The problem:

Almost every time any one of the DAGs is executed, no tasks from other DAGs will start until all the tasks from the first one finish. That is, if slow DAG_2 with 600 tasks starts, DAG_1 will have to wait for days to start even a single Task.

The Logs for the Scheduler look like this:

scheduler_1  | 
scheduler_1  | [2022-02-09 10:02:27,116] {scheduler_job.py:288} INFO - 4 tasks up for execution:
scheduler_1  |  
   
    
scheduler_1  |  
    
     
scheduler_1  |  
     
      
scheduler_1  |  
      
       
scheduler_1  | [2022-02-09 10:02:27,119] {scheduler_job.py:322} INFO - Figuring out tasks to run in Pool(name=default_pool) with 4 open slots and 4 task instances ready to be queued
scheduler_1  | [2022-02-09 10:02:27,119] {scheduler_job.py:349} INFO - DAG Slow_DAG has 2/2 running and queued tasks
scheduler_1  | [2022-02-09 10:02:27,119] {scheduler_job.py:357} INFO - Not executing 
       
         since the number of tasks running or queued from DAG Slow_DAG is >= to the DAG's max_active_tasks limit of 2 scheduler_1 | [2022-02-09 10:02:27,119] {scheduler_job.py:349} INFO - DAG Slow_DAG has 2/2 running and queued tasks scheduler_1 | [2022-02-09 10:02:27,119] {scheduler_job.py:357} INFO - Not executing 
        
          since the number of tasks running or queued from DAG Slow_DAG is >= to the DAG's max_active_tasks limit of 2 scheduler_1 | [2022-02-09 10:02:27,119] {scheduler_job.py:349} INFO - DAG Slow_DAG has 2/2 running and queued tasks scheduler_1 | [2022-02-09 10:02:27,120] {scheduler_job.py:357} INFO - Not executing 
         
           since the number of tasks running or queued from DAG Slow_DAG is >= to the DAG's max_active_tasks limit of 2 scheduler_1 | [2022-02-09 10:02:27,120] {scheduler_job.py:349} INFO - DAG Slow_DAG has 2/2 running and queued tasks scheduler_1 | [2022-02-09 10:02:27,120] {scheduler_job.py:357} INFO - Not executing 
          
            since the number of tasks running or queued from DAG Slow_DAG is >= to the DAG's max_active_tasks limit of 2 scheduler_1 | [2022-02-09 10:02:27,120] {scheduler_job.py:410} INFO - Setting the following tasks to queued state: scheduler_1 |

I have fixed this by setting

parallelism = 1000
default_pool_task_slot_count = 999

The reason why this occurs and why the solution works

We need to look at this method of the Scheduler: https://github.com/apache/airflow/blob/2.2.3/airflow/jobs/scheduler_job.py#L229
In it, the overall logic is the following:

Receive max_tis(== parallelism - active running tasks from the config) in the arguments. In my case that would be 30
Calculate how many free slots in all all Pools we have. In my case that would be 4.
Select the minimum and update the max_tis variable: max_tis = min(4, 30) = 4
Query the DB for tasks that are Scheduled in an unpaused DAGs that are running normally and order them by DAG execution date.
Limit the query by max_tis.
Loop over each returned task and check if we can run it. Run, if possible.

Now, since the tasks are ordered by execution date, this will return us tasks for a DAG that started first, which lets say was DAG_2. It has over 600 tasks. The LIMIT operation will return 4 of them. Each off these tasks cannot be run since there are already 2 tasks running and the max_active_tasks of the DAG is 2. Thus, we just wait till one of these tasks finish and start another task from the same DAG.

A reproduction repo for a Scheduling bug in AirFlow 2.2.3

Related tags

Overview

How to run

Setup

The problem:

The reason why this occurs and why the solution works

Owner

Ilya Strelnikov

Contains a Jupyter Notebook for calculating remaining plants required based on field/lathhouse data.

Application launcher and environment management

Static bytecode simulator

The third home of the bare Programming Language (1st there's my heart, the forest came second and then there's Github :)

An open source server for Super Mario Bros. 35

A site that went kinda viral that lets you put Bernie Sanders in places

Backend/API for the Mumble.dev, an open source social media application.

An Advanced Wordlist Library Written In Python For Acm114

A parser of Windows Defender's DetectionHistory forensic artifact, containing substantial info about quarantined files and executables.

Data on Free Food at MIT

This repo presents you the official code of "VISTA: Boosting 3D Object Detection via Dual Cross-VIew SpaTial Attention"

Enjoyable scripting experience with Python

BridgeWalk is a partially-observed reinforcement learning environment with dynamics of varying stochasticity.

Creates infinite amount of guilded accounts in seconds.

Multi-Process / Censorship Detection

An open-source hyper-heuristic framework for multi-objective optimization

Async-first dependency injection library based on python type hints

Web app for keeping track of buildings in danger of collapsing in the event of an earthquake

A modern Python build backend

京东自动入会获取京豆