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

enchancement: Limit outgoing connections to avoid killing routers #3311

Closed
mateon1 opened this issue Oct 17, 2016 · 3 comments
Closed

enchancement: Limit outgoing connections to avoid killing routers #3311

mateon1 opened this issue Oct 17, 2016 · 3 comments
Labels
need/analysis Needs further analysis before proceeding

Comments

@mateon1
Copy link
Contributor

mateon1 commented Oct 17, 2016

Version information: 0.4.5-dev-5ec0e59

Type: Enhancement

Priority: P2

Description:

As of now, IPFS tries to connect to as many peers as it can.
Unfortunately, most of the time it can connect to too many peers.

Right now, I have 3 daemons on my network, all of which have >170 connections.
This, for some reason kills/blocks/congests routers.

Right now, I can only rarely create new outgoing connections, which breaks a lot of services, causes DNS requests to fail 50% (or more) of the time, and many more issues.

This is not an issue of bandwidth, but adding a limit on the amount of connections will help to limit bandwidth as well.

@mateon1
Copy link
Contributor Author

mateon1 commented Oct 17, 2016

Clarification: This should be a config option, not a hard limit on the user.

@Kubuxu Kubuxu added the need/analysis Needs further analysis before proceeding label Nov 28, 2016
@lidel
Copy link
Member

lidel commented Dec 18, 2018

In 2017 connection manager shipped in v0.4.12.

The current default (600-900 connections) may be too high, but can be set to lower values in config file:

$ ipfs config --json Swarm.ConnMgr '{"HighWater": 100, "LowWater": 32, "Type": "basic", "GracePeriod": "15s"}'

Values above are just a guess: would be useful to get some real feedback from people with old routers and provide safe values under a predefined profile.

@Stebalien
Copy link
Member

Closing this in favor of the "don't kill routers" issue (#3320).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need/analysis Needs further analysis before proceeding
Projects
None yet
Development

No branches or pull requests

5 participants