VPatel5 commented on issue #69660: URL: https://github.com/apache/airflow/issues/69660#issuecomment-4969396288
> [@VPatel5](https://github.com/VPatel5) any updates to your scheduler memory leak? We have observed that the memory usage patterns differ across the three Airflow scheduler replicas over the last 4 days: **Scheduler 1 (apache-airflow-scheduler-695788959-vvwn4):** Memory grew gradually from ~640 MiB and plateaued at ~1.02 GiB around 07/12. Since then, usage has remained stable. **Scheduler 2 (apache-airflow-scheduler-695788959-g6t9f):** Memory exhibits frequent, short-lived spikes (roughly every few minutes, each ~15 MB above baseline) with a stable baseline. **Scheduler 3 (apache-airflow-scheduler-695788959-wdl59):** Memory is continuously and gradually increasing, from ~640 MiB to 1.14 GiB, **Scheduler 1:** <img width="2147" height="394" alt="Image" src="https://github.com/user-attachments/assets/04f1d31b-b554-45f9-9687-e1e5e439e0b8"; /> **Scheduler 2:** <img width="2146" height="408" alt="Image" src="https://github.com/user-attachments/assets/96b6554f-6b2b-4fb9-8b12-f86eb19cc2b3"; /> **Scheduler 3:** <img width="2151" height="396" alt="Image" src="https://github.com/user-attachments/assets/c4dd115b-9730-4264-ad4b-a10149127c1a"; /> Based on this data, I can't fully conclude that the memory leak is resolved — Scheduler 3 in particular is still trending upward. However, the behavior is definitely improved. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
