Skip to content
This repository has been archived by the owner on May 26, 2022. It is now read-only.

Hard limit on file descriptors #165

Closed
Stebalien opened this issue Feb 27, 2020 · 3 comments
Closed

Hard limit on file descriptors #165

Stebalien opened this issue Feb 27, 2020 · 3 comments
Labels
kind/enhancement A net-new feature or improvement to an existing feature

Comments

@Stebalien
Copy link
Member

The swarm should set a hard limit on new file descriptor consuming connections at 90% of the file descriptor limit. Otherwise, things break terribly.

@Stebalien Stebalien added the kind/enhancement A net-new feature or improvement to an existing feature label Feb 27, 2020
@Jorropo
Copy link

Jorropo commented Mar 2, 2020

I've planned to do it in Quality Transport. The struct returned by QTransport.Score(...) Score have an Fd field, transport can return the number of Fd used to open this connection, if not enough Fd are avaible the connection is gonna be put on hold.

@Stebalien
Copy link
Member Author

We already track which transports consume file descriptors, that's not the issue. This issue is simply about setting a hard upper limit.

@marten-seemann
Copy link
Contributor

Closing in favor of libp2p/go-libp2p#1260.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/enhancement A net-new feature or improvement to an existing feature
Projects
None yet
Development

No branches or pull requests

3 participants