Celery executor for distributed execution in Apache Airflow - Mini Project: Build & Apply

Celery Executor Setup for Distributed Task Execution in Airflow

📖 Scenario: You are setting up Apache Airflow to run tasks distributed across multiple worker machines. To do this, you will configure Airflow to use the Celery executor, which allows tasks to be sent to a queue and processed by multiple workers.This setup helps when you want to run many tasks in parallel and spread the work across several computers.

🎯 Goal: Configure Airflow to use the Celery executor by creating the necessary configuration settings. You will define the executor type, set up the broker URL for task messaging, and verify the configuration by printing the executor setting.

📋 What You'll Learn

Create a variable executor and set it to the string 'CeleryExecutor'.

Create a variable broker_url and set it to the string 'redis://localhost:6379/0' to specify the message broker.

Print the value of the executor variable to confirm the setup.

💡 Why This Matters

🌍 Real World

Using Celery executor in Airflow allows companies to run many data processing tasks in parallel across multiple machines, speeding up workflows.

💼 Career

Understanding how to configure distributed executors like Celery is important for DevOps engineers and data engineers managing scalable workflow systems.

1

Define the Airflow executor type

Create a variable called executor and set it to the string 'CeleryExecutor'.

Apache Airflow

# Create a variable called executor and set it to 'CeleryExecutor'
# Your code here

Hint

Use a simple assignment like executor = 'CeleryExecutor'.

2

Set the broker URL for Celery

Create a variable called broker_url and set it to the string 'redis://localhost:6379/0' to specify the Redis broker URL.

Apache Airflow

executor = 'CeleryExecutor'
# Create a variable called broker_url and set it to 'redis://localhost:6379/0'
# Your code here

Hint

Assign the Redis URL string to broker_url.

3

Add a configuration dictionary for Airflow

Create a dictionary called airflow_config with keys 'executor' and 'broker_url' set to the variables executor and broker_url respectively.

Apache Airflow

executor = 'CeleryExecutor'
broker_url = 'redis://localhost:6379/0'
# Create a dictionary airflow_config with keys 'executor' and 'broker_url'
# Your code here

Hint

Use airflow_config = {'executor': executor, 'broker_url': broker_url}.

4

Print the executor configuration

Write a print statement to display the value of airflow_config['executor'].

Apache Airflow

executor = 'CeleryExecutor'
broker_url = 'redis://localhost:6379/0'
airflow_config = {'executor': executor, 'broker_url': broker_url}
# Print the executor value from airflow_config
# Your code here

Hint

Use print(airflow_config['executor']) to show the executor.

Practice

1. What is the main purpose of using the CeleryExecutor in Apache Airflow?

easy

A. To replace the Airflow webserver with a faster interface

B. To store task logs locally on the scheduler machine

C. To execute tasks only on the local machine sequentially

D. To run tasks on multiple machines simultaneously for better scalability

Solution

1. Step 1: Understand CeleryExecutor's role

   CeleryExecutor allows Airflow to distribute task execution across multiple worker machines.

2. Step 2: Compare options with this role

   Only To run tasks on multiple machines simultaneously for better scalability describes running tasks on many machines at once, which matches CeleryExecutor's purpose.

3. Final Answer:

   To run tasks on multiple machines simultaneously for better scalability -> Option D

4. Quick Check:

   CeleryExecutor = distributed task execution [OK]

Hint: CeleryExecutor means many workers run tasks in parallel [OK]

Common Mistakes:

• Thinking CeleryExecutor runs tasks only locally
• Confusing CeleryExecutor with Airflow webserver
• Assuming CeleryExecutor stores logs locally

2. Which configuration setting in airflow.cfg enables the Celery executor?

easy

A. executor = LocalExecutor

B. executor = CeleryExecutor

C. executor = SequentialExecutor

D. executor = KubernetesExecutor

Solution

1. Step 1: Identify the executor setting in airflow.cfg

   The executor type is set by the executor parameter in airflow.cfg.

2. Step 2: Match the correct executor name for Celery

   To enable Celery executor, the value must be CeleryExecutor.

3. Final Answer:

   executor = CeleryExecutor -> Option B

4. Quick Check:

   executor setting = CeleryExecutor [OK]

Hint: Set executor = CeleryExecutor in airflow.cfg [OK]

Common Mistakes:

• Using LocalExecutor instead of CeleryExecutor
• Misspelling CeleryExecutor in config
• Confusing executor with other unrelated settings

3. Given this Airflow CeleryExecutor setup, what happens when a DAG task is triggered?

1. Scheduler sends task to message broker
2. Worker picks task from broker queue
3. Worker executes task and updates database

medium

A. Task is distributed to a worker and executed asynchronously

B. Task runs only on the scheduler machine

C. Task is executed immediately by the scheduler without queue

D. Task fails because CeleryExecutor does not use a message broker

Solution

1. Step 1: Understand CeleryExecutor task flow

   The scheduler sends tasks to a message broker, which workers listen to and execute asynchronously.

2. Step 2: Match the correct description

   Task is distributed to a worker and executed asynchronously correctly describes the asynchronous distributed execution via workers.

3. Final Answer:

   Task is distributed to a worker and executed asynchronously -> Option A

4. Quick Check:

   CeleryExecutor = async distributed tasks [OK]

Hint: Tasks go to workers via broker, run async [OK]

Common Mistakes:

• Thinking tasks run on scheduler directly
• Ignoring the message broker role
• Assuming synchronous execution

4. You configured Airflow to use CeleryExecutor but tasks are stuck in the queue and never run. What is the most likely cause?

medium

A. The DAG files are missing from the scheduler

B. The scheduler is not running

C. The message broker (e.g., RabbitMQ or Redis) is not running or unreachable

D. The Airflow webserver is down

Solution

1. Step 1: Identify the role of the message broker

   CeleryExecutor relies on a message broker to queue tasks for workers.

2. Step 2: Understand why tasks get stuck

   If the broker is down or unreachable, tasks remain queued and are not delivered to workers.

3. Final Answer:

   The message broker (e.g., RabbitMQ or Redis) is not running or unreachable -> Option C

4. Quick Check:

   Broker down = tasks stuck [OK]

Hint: Check if message broker service is running [OK]

Common Mistakes:

• Blaming scheduler when broker is down
• Ignoring broker connectivity issues
• Assuming webserver affects task execution

5. You want to improve task execution reliability using CeleryExecutor. Which combination of components should you configure to ensure tasks are not lost if a worker crashes?

hard

A. Use a persistent message broker like RabbitMQ and enable result backend in the database

B. Use LocalExecutor and disable the message broker

C. Run all tasks on the scheduler machine without workers

D. Use CeleryExecutor without a result backend

Solution

1. Step 1: Understand reliability needs in CeleryExecutor

   To avoid task loss, the message broker must persist tasks and results must be stored reliably.

2. Step 2: Identify correct components

   RabbitMQ is a persistent broker; enabling a result backend in the database stores task states safely.

3. Final Answer:

   Use a persistent message broker like RabbitMQ and enable result backend in the database -> Option A

4. Quick Check:

   Persistent broker + result backend = reliable tasks [OK]

Hint: Persistent broker + result backend prevent task loss [OK]

Common Mistakes:

• Disabling message broker with CeleryExecutor
• Not enabling result backend causes lost states
• Running tasks only on scheduler reduces reliability