[
https://issues.apache.org/jira/browse/AIRFLOW-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888687#comment-16888687
]
Ash Berlin-Taylor commented on AIRFLOW-4593:
--------------------------------------------
[~mmorawski] Thanks for confirming. You don't have the issue describe in the
gist then, but instead the one in the ticket.
The interesting thing is that the memory isn't returned back to the OS even if
you do {{docker stop airflow_scheduler}}? That .... shouldn't be possible with
a docker container.
Could you {{egrep -r '3142|3141'}} in your logs/ folder, to see if we can see
what process 31424/31425 likely were?
> Memory leak in Airflow scheduler
> --------------------------------
>
> Key: AIRFLOW-4593
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4593
> Project: Apache Airflow
> Issue Type: Bug
> Components: scheduler
> Affects Versions: 1.10.2
> Reporter: Nikhil SInghal
> Priority: Major
> Attachments: Screenshot 2019-05-30 at 3.19.33 PM.png
>
>
> We are running Apache Airflow on Kubernetes. When I see my Grafana Dashboard
> I see that the memory used is consistently increasing. Can anyone give me
> some pointers for how can I debug this or with existing issues/solutions
> related to this.
> This is a sharp increase in Airflow scheduler and slow increase for worker
> and webserver
> !Screenshot 2019-05-30 at 3.19.33 PM.png|width=100%!
>
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
