-
Notifications
You must be signed in to change notification settings - Fork 971
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
A lot of "handling wantlist overflow" logs that makes load on CPU (shwap) #3903
Comments
Thanks for reporting this. Hopefully, this is gonna be fixed in the next patch alongside other Bitswap improvements on the way. |
even we had the same issue, glad to know that itll be fixed in the next version! |
I can confirm that this issue still exists on the latest version of Shwap
This leads to memory leaks causing the server to eventually run out of memory over time. |
The latest release didn't have any fixes related to this yet. |
adding our logs too, cpu is slowly creeping up then it leads to 100% usage spikes and ends up on 100% cpu usage on all cores, some logs:
|
Thanks, just keeping you guys in the loop, we are here to support in terms of logs etc and what ever insight you guys need. Keep up the good work. From what I understand this is a CWE-400 scenario leading to both CPU and memory high usage and eventual swap getting filled. So after digging into what found out logs say the same issue mentioned here but not sure about the version used https://security.snyk.io/vuln/SNYK-GOLANG-GITHUBCOMIPFSBOXOBITSWAPSERVER-5518110 Hoping this helps 🤝 |
This is a WIP fix for this issue and you can try it already |
Please try our recent release. It must resolve this issue altogether |
Closing it for now, but feel free to report if its not fixed on your side |
Celestia Node version
v0.18.3-mocha
OS
ubuntu 22.04
Install tools
System version: amd64/linux
Golang version: go1.23.2
Others
configs are default persisted over init command, only core ports are changed.
Steps to reproduce it
Expected result
There are no a lot of logs on handling wantlist overflow
Actual result
There are a lot of logs on handling wantlist overflow
Relevant log output
Is the node "stuck"? Has it stopped syncing?
no
Notes
I also observe these logs but in less amount on other nodes:
Semantic version: v0.16.2-mocha
Commit: 3cbf435
Build Date: Wed Oct 2 11:08:31 UTC 2024
System version: amd64/linux
Golang version: go1.23.1
Semantic version: v0.16.0
Commit: 6744f64
Build Date: Wed Sep 11 10:31:18 UTC 2024
System version: amd64/linux
Golang version: go1.23.1
The text was updated successfully, but these errors were encountered: