-
Notifications
You must be signed in to change notification settings - Fork 480
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
Frequent restarts on k8s #97
Comments
likely related to #92? Try with a build from current master. |
I've rebuilt from master, will let it run for a day or so and get back here |
I'm still getting restarts even with the HEAD:
It's been about 1 year or so since I touched Go so I'm not entirely up to date on how to diagnose this. Any help I can get with this would be great! Thanks. |
I have the same issue with the current latest commit ( I added limits to have imageproxy killed and now it gets killed all the time. I start imageproxy with this: The memory limit in k8s is 512Mi. Here's the state of things on my end currently:
|
I'm also running into this. With memory limit of 1Gi, very frequent restart. Increased to 2Gi, less frequent but still. Now at 3Gi and it restarted once after 20 minute... |
When loading a web page with a lot of proxy URLs so that the browser attempts to download them all immediately, the process is killed because it's out of memory. I don't know how to get around this, since it's not something I can control in browsers. It seems like imageproxy should be rate limiting these requests at some point to avoid OOM issues. |
After using imageproxy for 2 weeks it looks like it restarts a lot because of
OOMKilled
(out of memory errors).Here's the number of restarts:
Here's the description of one pod:
The logs are only after restart and there is no hint as to why there so much memory being used.
The upper memory limit (from the config) is
1Gi
. Probably a memory leak right? Any idea how to diagnose this?The text was updated successfully, but these errors were encountered: