reqwest: "Too many open files" w/ Async Client
I’ve been developing the tooling for an apt replacement with the async client, which may need to fetch a couple dozen files at the same time (depending on how many sources are active and what files those sources’ release files point to).
The following error occurs when sharing a single async::Client across all connections:

Is this something that could be handled better by reqwest? Perhaps return a NotReady when there’s too many files open.
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 22 (10 by maintainers)
Commits related to this issue
- [0] add concurrency limit on download streams * else, runaway async http requests flood the system's capacity for open sockets and get a "too many files open" error (see: https://github.com/seanm... — committed to aguestuser/dl by aguestuser 7 years ago
- fix: Limit number of connections open for GCS interactions What? This PR adds an in-house implementation for connections limiting, via semaphore. Ideally, the connection pool would expose a limit to... — committed to matter-labs/zksync-era by EmilLuta 2 years ago
- fix: Limit number of connections open for GCS interactions (#3637) ## What? This PR adds an in-house implementation for connections limiting, via semaphore. Ideally, the connection pool would expose... — committed to matter-labs/zksync-era by EmilLuta 2 years ago
It seems to be continually creating new
socketandconnectdescriptors without closing them.