Pain point · Performance · Causes churn
Scheduler memory leak leaves tasks stuck in scheduled state
2 source threads · first seen 2021-03 · last seen 2025-09
Summary
On Airflow 2.0.1 the scheduler grows to several GB over days and tasks get stuck; the old option to restart it periodically is gone.
- Affects
- Teams on KubernetesExecutor
- Workaround
- Restart the scheduler
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“Over time, memory consumption keeps increasing until swap is heavily used and eventually the system hits OOM”
“the scheduler has a memory leak and over past 4 days it has reached up to 6GB of memory utilization”