swarm: better backoff logic
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.9k
- Forks
- 1.3k
- Avg merge
- 13d 21h
- Merged PRs (30d)
- 1
Description
- We should try to distinguish between local failures and remote failures. At the very least, we should be resetting our backoffs when new links/routes come online.
- We should probably be backing off on a per multiaddr basis, not a per peer basis (unless we establish a connection to the peer and it tells us to to away (need a new protocol for that, related to https://github.com/libp2p/go-libp2p/issues/238).
Came up in: https://github.com/libp2p/go-libp2p-kad-dht/issues/96
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the swarm's existing backoff behavior and the handling of new links or routes. Define how local failures differ from remote failures, when new routes reset backoffs, and whether backoff state is per multiaddr or per peer. Review the related issue #238 and the originating go-libp2p-kad-dht issue #96 before determining the completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100