-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gcsfusecsi-metrics-collector container getting OOM killed #373
Comments
Hi @pdfrod, this is interesting behavior. Can you provide GKE cluster version? Can you provide the number of pods that you are running on each node? Can you also confirm if this is causing issues in your workload? In this case, I can provide the steps to disable metrics exporting. Could you share the Cluster ID with me? You can get the id by running |
Sure, here's the info you requested @hime.
I should probably mention that I don't remember seeing this problem when there were just a couple of deployments using this driver. Now that I have 12 deployments using the driver, I'm seeing OOM kills of the metrics collector every day. If there's a way to disable the metrics collector container, that would be even better as currently I'm not using those metrics. Let me know if you need more info. |
Cool, I'll give that a try. Thanks! |
Cool, thanks a lot! Since I've disabled metrics on my cluster I haven't seen any OOM kills, so it's looking good so far. |
I'm experiencing occasional OOM kills of the
gcsfusecsi-metrics-collector
container (part ofgcsfusecsi-node
DaemonSet). This container has a somewhat low memory limit (30Mi). Is there a way to costumize the memory limit of this container?The text was updated successfully, but these errors were encountered: