Pods accumulate lots of RAM
robkuehl opened this issue · 2 comments
robkuehl commented
Checks
- I have checked for existing issues.
- This report is about the
User-Community Airflow Helm Chart.
Chart Version
8.7.1
Kubernetes Version
Client Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.1", GitCommit:"8f94681cd294aa8cfd3407b8191f6c70214973a4", GitTreeState:"clean", BuildDate:"2023-01-18T15:51:24Z", GoVersion:"go1.19.5", Compiler:"gc", Platform:"darwin/arm64"}
Server Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.12+7566c4d", GitCommit:"22147459669562208c3082141eece03824c0a417", GitTreeState:"clean", BuildDate:"2022-10-24T10:40:54Z", GoVersion:"go1.17.12", Compiler:"gc", Platform:"linux/amd64"}Helm Version
version.BuildInfo{Version:"v3.11.1", GitCommit:"293b50c65d4d56187cd4e2f390f0ada46b4c4737", GitTreeState:"clean", GoVersion:"go1.19.5"}Description
The Pods accumulate a lot of RAM quickly. Is this behavior normal?
Relevant Logs
No response
Custom Helm Values
No response
thesuperzapper commented
@robkuehl this is not typical, so you might want to check if any of your dag definitions have a memory leak (note, I am talking about the python definitions, not the dags themselves).
Or if you have a custom airflow image, anything you have changed in it could be the cause.
Its also possible that you have found a bug in airflow itself, which version are you using?
stale commented
This issue has been automatically marked as stale because it has not had activity in 60 days.
It will be closed in 7 days if no further activity occurs.
Thank you for your contributions.
Issues never become stale if any of the following is true:
- they are added to a Project
- they are added to a Milestone
- they have the
lifecycle/frozenlabel