CapBananoid commented on issue #14924: URL: https://github.com/apache/airflow/issues/14924#issuecomment-911791784
I did nothing but a rm and it dropped quite immediately (sorry the memory is brought back by prometheus andd you have delay but what I can tell you is that it dropped within 15s after I did the rm) I just did it on my dev instance in fact, same result The container is the scheduler, I run separate container for each service, this is the one with the command "airflow scheduler -n -1" I don't think the scheduler can restart by itself, if it had been the case then kubernetes would have shown a restart and it's not the case I can tell you that the type of memory that is shown to grow is the one from the prometheus metric called container_memory_cache -- 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]
