Skip to content
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

Memory leaking leads to OOMs #259

Closed
evgkrsk opened this issue Nov 2, 2023 · 7 comments
Closed

Memory leaking leads to OOMs #259

evgkrsk opened this issue Nov 2, 2023 · 7 comments

Comments

@evgkrsk
Copy link

evgkrsk commented Nov 2, 2023

Somehow all spegel's pods in my test cluster have linearly increasing memory usage that already killed one of pods twice in 1 day due to OOM (limit is 320Mi).

How can I help to debug such issue?

@evgkrsk
Copy link
Author

evgkrsk commented Nov 10, 2023

Seems like disabling tags resolution helps to prevent OOMs:
image

@phillebaba
Copy link
Member

That is an interesting finding. I can't really see how resolving tags would effect memory usage. Could I ask which version of Spegel you are using and what Kubernetes flavor you are deploying on.

@evgkrsk
Copy link
Author

evgkrsk commented Nov 11, 2023

v0.0.14 image and vanilla k8s-1.23 on bare-metal.

@phillebaba
Copy link
Member

@evgkrsk I have not come up with a method of reproducing this. I just released v0.0.15 which contains the fix libp2p/go-libp2p-kad-dht#960 which seems to have caused memory leaks during lookups. Could you try this new version and see if you experience the same issues?

@evgkrsk
Copy link
Author

evgkrsk commented Nov 29, 2023

I have upgraded my test cluster to v0.0.16 and so far memory usage decreased by an order of magnitude (300Mi -> 50Mi). Lets wait a bit to get more statistics...

@phillebaba
Copy link
Member

@evgkrsk any updates?

@evgkrsk
Copy link
Author

evgkrsk commented Dec 5, 2023

Issue resolved :-)
image

@evgkrsk evgkrsk closed this as completed Dec 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants