High availability configuration in Apache Airflow - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable the scheduler in Airflow's configuration for high availability.

Apache Airflow

[scheduler]
enabled = [1]

Drag options to blanks, or click blank then click option'

ATrue

BFalse

CNone

Dauto

Attempts:

3 left

💡 Hint

Common Mistakes

Setting enabled to False disables the scheduler.

Using 'None' or 'auto' are invalid values here.

Setting enabled = True in the scheduler section activates the scheduler, which is necessary for high availability setups.

2fill in blank

medium

Complete the command to start the Airflow scheduler in high availability mode.

Apache Airflow

airflow scheduler [1]

Drag options to blanks, or click blank then click option'

A--single-threaded

B--num_runs 0

C--daemon

D--high-availability

Attempts:

3 left

💡 Hint

Common Mistakes

Using --single-threaded limits scheduler concurrency.

The --num_runs 0 flag runs scheduler only once.

There is no --high-availability flag in airflow scheduler.

The --daemon flag runs the scheduler in the background, which is typical for high availability setups.

3fill in blank

hard

Fix the error in the Airflow configuration to enable the executor for high availability.

Apache Airflow

[core]
executor = [1]Executor

Drag options to blanks, or click blank then click option'

ASequential

BCelery

CLocal

DDebug

Attempts:

3 left

💡 Hint

Common Mistakes

SequentialExecutor runs tasks one at a time, not suitable for HA.

LocalExecutor runs tasks locally, limited for HA.

DebugExecutor is for debugging only.

The CeleryExecutor is used for high availability as it supports distributed task execution.

4fill in blank

hard

Fill both blanks to configure the database connection string for Airflow high availability.

Apache Airflow

sql_alchemy_conn = [1]://[2]@localhost/airflow_db

Drag options to blanks, or click blank then click option'

Apostgresql+psycopg2

Buser:password

Cmysql+pymysql

Dadmin:admin123

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing MySQL dialect with PostgreSQL credentials.

Using incomplete or incorrect connection string format.

The connection string format is dialect+driver://username:password@host/dbname. For example, postgresql+psycopg2://user:password@localhost/airflow_db.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that maps worker names to their status if status is 'active' in Airflow high availability monitoring.

Apache Airflow

worker_status = { [1]: [2] for [3] in workers if [2] == 'active' }

Drag options to blanks, or click blank then click option'

Aworker.name

Bworker.status

Cworker

Dstatus

Attempts:

3 left

💡 Hint

Common Mistakes

Using undefined variables like 'status' instead of 'worker.status'.

Swapping keys and values in the dictionary.

This comprehension creates a dictionary where keys are worker names and values are their status, but only for active workers.

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