# Airflow Executor

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

**Field:** Data Engineering  
**Category:** Orchestration  
**Also known as:** Executor (Airflow), CeleryExecutor, KubernetesExecutor, LocalExecutor

## Think of it like

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

## 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.

## 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.

## Common mistake

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

## Three principles

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

## Related terms

- [Airflow Scheduler](https://learn.benibix.com/term/data/airflow-scheduler)
- [Apache Airflow](https://learn.benibix.com/term/data/apache-airflow)
- [Airflow Task](https://learn.benibix.com/term/data/airflow-task)
- [Airflow Metadata Database](https://learn.benibix.com/term/data/airflow-metadata-database)

## Told apart from

- [Airflow Scheduler vs Airflow Executor](https://learn.benibix.com/compare/airflow-scheduler-vs-airflow-executor): People think the Airflow scheduler runs the tasks. It only decides which tasks are ready and puts them in a queue. The executor takes them from the queue and runs them, on one machine or many. A slow queue and a slow task have different fixes.

![DAG files in a folder are read by a DAG processor into a metadata database. The scheduler reads the database, decides which tasks are ready and hands them to an executor, which runs them on workers. The web UI reads the same database.](https://learn.benibix.com/diagrams/airflow-architecture.svg)

---

Source: https://learn.benibix.com/term/data/airflow-executor
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-17
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
