-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Bug: Increasing Pod Memory Usage for Push Service #1945
Comments
This seems a bit unusual. |
I made a temp workaround:
This will try to reuse conn if absent, otherwise GetConn. Not sure if this is safe solution. WDYT? |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
this issue has fixed in release-v3.8, I recommend you update to new version. If you run into any new issues, please reopen this issue or create a new one. |
What happened?
Server version 3.5.0. Push service consumed too much memory. Possible memory leak?
What did you expect to happen?
stable memory usage
How can we reproduce it (as minimally and precisely as possible)?
This is a prometheus metrics. Queried by
sum (container_memory_working_set_bytes{image!="",pod_name=~"$Pod",namespace="$namespace"}) by (pod_name)
Anything else we need to know?
No response
version
Cloud provider
OS version
Install tools
The text was updated successfully, but these errors were encountered: