High availability configuration in Apache Airflow - Time & Space Complexity

Time Complexity: High availability configuration

O(n)

Understanding Time Complexity

When setting up high availability in Airflow, we want to know how the system handles more tasks and workers.

We ask: How does adding more workers or tasks affect the system's work and response time?

Scenario Under Consideration

Analyze the time complexity of the following Airflow scheduler and worker setup.

from airflow import DAG
from airflow.operators.bash import BashOperator
from datetime import datetime

def create_task(task_id, dag):
    return BashOperator(
        task_id=task_id,
        bash_command='echo Hello',
        dag=dag
    )

dag = DAG('ha_dag', start_date=datetime(2024,1,1))

tasks = [create_task(f'task_{i}', dag) for i in range(100)]

This code creates 100 tasks in a DAG, simulating a workload for a high availability Airflow setup.

Identify Repeating Operations

Look for loops or repeated actions that affect performance.

• Primary operation: Creating and scheduling each task in the DAG.
• How many times: 100 times, once per task.

How Execution Grows With Input

As the number of tasks grows, the scheduler must handle more work.

Input Size (n)	Approx. Operations
10	10 task creations and scheduling steps
100	100 task creations and scheduling steps
1000	1000 task creations and scheduling steps

Pattern observation: The work grows directly with the number of tasks; doubling tasks doubles the work.

Final Time Complexity

Time Complexity: O(n)

This means the time to schedule tasks grows in a straight line with the number of tasks.

Common Mistake

[X] Wrong: "Adding more workers makes scheduling time stay the same no matter how many tasks there are."

[OK] Correct: Even with more workers, the scheduler still processes each task, so the total scheduling work grows with tasks.

Interview Connect

Understanding how task scheduling scales helps you design reliable Airflow setups that keep running smoothly as work grows.

Self-Check

"What if we split the tasks into multiple DAGs running in parallel? How would the time complexity of scheduling change?"

Practice

1. What is the main purpose of configuring high availability in Apache Airflow?

easy

A. To reduce the number of DAGs in the system

B. To keep Airflow running even if some components fail

C. To speed up the Airflow UI loading time

D. To limit the number of users accessing Airflow

Solution

1. Step 1: Understand high availability concept

   High availability means the system keeps working even if parts fail.

2. Step 2: Apply to Airflow context

   In Airflow, this means tasks and services continue running despite failures.

3. Final Answer:

   To keep Airflow running even if some components fail -> Option B

4. Quick Check:

   High availability = system stays up despite failures [OK]

Hint: High availability means no downtime during failures [OK]

Common Mistakes:

• Confusing high availability with performance optimization
• Thinking it limits users or DAGs
• Assuming it only affects the UI

2. Which executor is commonly used in Airflow for high availability setups?

easy

A. SequentialExecutor

B. DebugExecutor

C. LocalExecutor

D. CeleryExecutor

Solution

1. Step 1: Recall executor types in Airflow

   SequentialExecutor runs tasks one by one, LocalExecutor runs tasks locally in parallel.

2. Step 2: Identify executor for distributed task handling

   CeleryExecutor uses workers and message brokers for distributed task execution, suitable for high availability.

3. Final Answer:

   CeleryExecutor -> Option D

4. Quick Check:

   Distributed task handling = CeleryExecutor [OK]

Hint: CeleryExecutor enables distributed task execution [OK]

Common Mistakes:

• Choosing SequentialExecutor which is single-threaded
• Confusing LocalExecutor with distributed execution
• Selecting DebugExecutor which is for testing only

3. Given this Airflow configuration snippet for high availability, what is the role of Redis?

[celery]
broker_url = redis://localhost:6379/0

medium

A. Stores task results permanently

B. Manages the Airflow metadata database

C. Acts as a message broker between scheduler and workers

D. Runs the Airflow webserver

Solution

1. Step 1: Identify Redis role in CeleryExecutor

   Redis is used as a message broker to pass task messages between scheduler and workers.

2. Step 2: Differentiate Redis from other components

   Redis is not for storing results permanently or running webserver or metadata DB.

3. Final Answer:

   Acts as a message broker between scheduler and workers -> Option C

4. Quick Check:

   Redis = message broker in CeleryExecutor [OK]

Hint: Redis brokers messages between scheduler and workers [OK]

Common Mistakes:

• Thinking Redis stores metadata or results
• Confusing Redis with PostgreSQL database
• Assuming Redis runs the webserver

4. You configured Airflow with CeleryExecutor but tasks are not being distributed to workers. Which configuration mistake could cause this?

medium

A. Using SQLite as the metadata database

B. Setting broker_url to a Redis server

C. Running multiple scheduler instances

D. Enabling high availability mode in webserver

Solution

1. Step 1: Understand metadata database requirements

   CeleryExecutor requires a robust metadata database like PostgreSQL, not SQLite.

2. Step 2: Identify why SQLite causes issues

   SQLite locks the database and does not support concurrent writes well, blocking task distribution.

3. Final Answer:

   Using SQLite as the metadata database -> Option A

4. Quick Check:

   SQLite blocks concurrency, breaks CeleryExecutor [OK]

Hint: Use PostgreSQL, not SQLite, for CeleryExecutor metadata DB [OK]

Common Mistakes:

• Assuming Redis broker_url is wrong when it is correct
• Thinking multiple schedulers cause task distribution failure
• Confusing webserver settings with task distribution

5. To achieve high availability for Airflow's scheduler, which setup is recommended?

hard

A. Run multiple scheduler instances with PostgreSQL backend and CeleryExecutor

B. Run a single scheduler instance with SQLite backend

C. Run multiple webservers without a scheduler

D. Use LocalExecutor with a single scheduler instance

Solution

1. Step 1: Understand scheduler high availability needs

   Multiple scheduler instances increase reliability and avoid single point of failure.

2. Step 2: Combine with proper backend and executor

   PostgreSQL supports concurrency well; CeleryExecutor enables distributed task execution.

3. Step 3: Eliminate incorrect options

   SQLite and single scheduler limit availability; webservers alone don't schedule tasks; LocalExecutor is not distributed.

4. Final Answer:

   Run multiple scheduler instances with PostgreSQL backend and CeleryExecutor -> Option A

5. Quick Check:

   Multiple schedulers + PostgreSQL + CeleryExecutor = HA scheduler [OK]

Hint: Multiple schedulers + PostgreSQL + CeleryExecutor = high availability [OK]

Common Mistakes:

• Using SQLite which blocks concurrency
• Running only one scheduler instance
• Confusing webserver role with scheduler