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

Work with the connection manager #65

Closed
Stebalien opened this issue Apr 4, 2019 · 3 comments · Fixed by #75
Closed

Work with the connection manager #65

Stebalien opened this issue Apr 4, 2019 · 3 comments · Fixed by #75
Assignees

Comments

@Stebalien
Copy link
Member

We should integrate with the connection manager to deprioritize relay-hop connections when under heavy load.

@Stebalien
Copy link
Member Author

See: ipfs/kubo#6166 (comment).

@vyzo
Copy link
Contributor

vyzo commented Apr 5, 2019

We also need a mechanism to tag connections used as relay reservations, so that we don't drop them off the relay unnecessarily.
I think we need a RESERVE message, which should tag the connection in the cm.

@vyzo
Copy link
Contributor

vyzo commented Apr 12, 2019

So given our observations regarding relay traffic and the discussion in #67 I think we want to do the opposite when operating as a relay. We should tag connections according to their hop count, so that when the connection manager decides to prune, we prune the idle connections first.
We might also want to have an option to explicitly enable that, as it could wreak havoc with the tagging from other subsystems.

@ghost ghost assigned vyzo May 7, 2019
@ghost ghost added the status/in-progress In progress label May 7, 2019
@ghost ghost removed the status/in-progress In progress label May 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants