deepak4babu opened a new issue, #42195: URL: https://github.com/apache/airflow/issues/42195
### Apache Airflow version Other Airflow 2 version (please specify below) ### If "Other Airflow 2 version" selected, which one? 2.8.3 ### What happened? We started to use deferrable operators and sensors from 2 weeks back. As part of it, we started using triggerer. The triggerer container memory is increasing steadily, even when no triggers are running. <img width="951" alt="airflow-triggerer-memory-leak-2 8 3" src="https://github.com/user-attachments/assets/74342e88-74a8-4703-a753-6204ae58e268";> ### What you think should happen instead? Memory consumption of idle triggerer should be less and does not increase ### How to reproduce Deploy triggerer in kubernetes with airflow version 2.8.3. Monitor for 24hrs ### Operating System kubernetes ### Versions of Apache Airflow Providers apache-airflow-providers-celery==3.6.1 apache-airflow-providers-common-io==1.4.0 apache-airflow-providers-common-sql==1.11.1 apache-airflow-providers-ftp==3.7.0 apache-airflow-providers-http==4.10.0 apache-airflow-providers-imap==3.5.0 apache-airflow-providers-smtp==1.8.0 apache-airflow-providers-sqlite==3.7.1 ### Deployment Other ### Deployment details Airflow version: 2.8.3 Python version: 3.9.x Database: Postgres 13 Kubernetes details: Azure kubernetes service Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 k8s Server Version: v1.29.4 Dags are packaged as python packages and installed in the airflow base image. Airflow triggerer is deployed using our custom helm chart, which is just a modified version of official one. ### Anything else? _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
