---
title: "Discussion on \"How I Found and Fixed a Memory Leak in Celery's ETA Task Queue\" | Hashnode"
description: "Discussion on \"How I Found and Fixed a Memory Leak in Celery's ETA Task Queue\". Tracing an unbounded prefetch in the ETA scheduling path — and contributing the fix upstream."
url: "https://hashnode.com/posts/how-i-found-and-fixed-a-memory-leak-in-celery-s-eta-task-queue/69c4065d10e664c5dabbcaa3"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How I Found and Fixed a Memory Leak in Celery's ETA Task Queue](https://musashiforge.hashnode.dev/how-i-found-and-fixed-a-memory-leak-in-celery-s-eta-task-queue?utm_source=hashnode&utm_medium=feed)

Tracing an unbounded prefetch in the ETA scheduling path — and contributing the fix upstream.

Mar 25 · 15 min read · musashiforge.hashnode.dev  
Read the article

-   [#monitoring](https://hashnode.com/tag/monitoring)
-   [#celery](https://hashnode.com/tag/celery)
-   [#python](https://hashnode.com/tag/python)
-   [#memory-leak](https://hashnode.com/tag/memory-leak)
-   [#distributed-system](https://hashnode.com/tag/distributed-system)
-   [#opensource](https://hashnode.com/tag/opensource)
-   [#debugging](https://hashnode.com/tag/debugging)

## Written by

[sandeep kesarwani](https://hashnode.com/@musashiforge)

@musashiforge · Delhi, India

  
[View profile](https://hashnode.com/@musashiforge)

A thousand days of practice to forge. Ten thousand to refine.

I'm Sandeep. I build distributed systems at the intersection of industrial IoT, real-time analytics, and AI infrastructure. For the past 8 years, I've been the engineer who gets called when the system is on fire — OOM-killed workers, runaway queries, architectures that don't scale.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.