-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
IPFS starts too many new connections on add #4102
Comments
This mean that connection listener is not working in I suspect something might be wrong with |
After digging a bit more, turns out that:
|
Fix is in libp2p/go-libp2p-swarm#26, bubbling it up is probably blocked by #4094. |
It should be bubble up in 0.4.10, it is a big bug that hits many users and makes go-ipfs 1. hard to use 2. seem more resource expensive than it can be. |
Oh, I forgot 4.10 is out. |
Reopening as libp2p/go-libp2p-swarm#26 isn't yet propagated and this got auto-closed. |
fixes #4102 (fixed in go-libp2p-swarm) License: MIT Signed-off-by: Steven Allen <[email protected]>
fixes #4102 (fixed in go-libp2p-swarm) License: MIT Signed-off-by: Steven Allen <[email protected]>
fixes #4102 (fixed in go-libp2p-swarm) License: MIT Signed-off-by: Steven Allen <[email protected]>
Version information:
current master at 181dd00
Type:
Bug
Severity:
High
Description:
When adding a large file the daemon starts creating many new connections eventually failing with
too many open files
error. This can be easily reproduced by running the daemon and thendd bs=1M if=/dev/urandom count=1000 | ipfs add --pin=false
Script/command for daemon monitoring:
When the add is running the daemon sometimes starts creating way more new connections(SYN_SENT) than it should, up to 1500 when it runs out of FD limit.
This is directly causing #3792 and is likely one of the reasons why many lower-end routers can't handle ipfs.
The text was updated successfully, but these errors were encountered: