Skip to content
BENIBIX Learn

Airflow Executor

Data🗓️ OrchestrationApache Airflow

Also known as Executor (Airflow), CeleryExecutor, KubernetesExecutor, LocalExecutor

The Airflow part that runs queued tasks. It can use one machine or many.

Think of it like

The teacher rings the bell. The executor is the person who sends each child to the right room.

Example

A small team runs Airflow on one server with the local kind. A bigger team uses the Kubernetes kind, so each task gets its own pod.

Why it matters

This part sets how many tasks run at once and how much memory each gets. Outgrowing it is the most common reason Airflow gets slow.

Definition

The Airflow executor decides where and how queued tasks run. The local one runs them as processes on the same machine. The Celery one sends them to a pool of worker machines. The Kubernetes one starts a fresh pod for each task. You pick one in Airflow's settings. The local one is the default.
The executor is on the right. It turns the scheduler's queue into real work on workers.

Common mistake

Keeping the local executor as the work grows. One machine runs out of room, and tasks wait in the queue for hours.

Key takeaways

  1. 1
    Runs the work. Takes tasks from the scheduler's queue.
  2. 2
    Local or remote. One machine, a worker pool or pods.
  3. 3
    Sets the limits. How many tasks run at once.

Compare