potiuk commented on issue #27589: URL: https://github.com/apache/airflow/issues/27589#issuecomment-1311814947
The `container_memory_working_set_bytes` should be non-evictable memory, so I think this is not a cache. I think it will cause oom, but I also think this is one of your modifications - airflow does not seem to thek more memory, it looks like your working set. I recommend you to install completely "vanilla" airflow - Helm and Image and see if you see the same growth. If not (I expect that), you can apply your modifications one-by-one and see which one causes the problem. This is the best way I can advice on diagnosing those kind of issues. It's extremely hard to know what it is without applying such technique. It can be antyhing - scripts running in background for example. The fact that you do not see it in airflow's container, would suggest that it might be another container - init container maybe even liveness probe running and leaving smth behind. -- 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]
