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

IPLD Resolver: Manage outgoing connections #462

Closed
aakoshh opened this issue Mar 2, 2023 · 0 comments
Closed

IPLD Resolver: Manage outgoing connections #462

aakoshh opened this issue Mar 2, 2023 · 0 comments
Labels

Comments

@aakoshh
Copy link
Contributor

aakoshh commented Mar 2, 2023

#466 assume that it is possible to open new outgoing connections to peers in subnets we want to resolve content from. There is a limit on incoming connections in #465, so we might have to try a few peers until we find one with free capacity, but we assume we won't run into our own restriction, that if we need to connect to a new subnet and we don't have a connection to it, we'll make room.

For this reason, #465 sets no limit on outgoing connections. We have to make sure though, that the connections opened during peer discovery (unless it's using UDP) and Bitswap don't stay open forever.

One way of achieving the latter is to track in the Content behaviour who we are connected to and close down connections in subnets which are served by too many peers already.

@jsoares jsoares transferred this issue from consensus-shipyard/ipc-libs Dec 19, 2023
@jsoares jsoares added the s:ipc label Dec 19, 2023
@jsoares jsoares closed this as not planned Won't fix, can't repro, duplicate, stale Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants