tcp: detect reuseport issues
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.9k
- Forks
- 1.3k
- Avg merge
- 13d 21h
- Merged PRs (30d)
- 1
Description
See https://github.com/ipfs/go-ipfs/issues/3718#issuecomment-350925123
It should be possible for us to notice that TCP connections keep failing and occasionally retry them without reuseport. If the connection succeeds without reuseport, we should then disable it.
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 reading the linked go-ipfs issue comment, then locate the TCP connection handling and reuseport logic in go-libp2p. The change is done when repeated TCP failures can trigger retries without reuseport, and a successful fallback disables reuseport for later connections.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100