livepeer / livepeer/go-livepeer
Consider backoff/rate limit for discovery requests on B
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 586
- Forks
- 226
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 19
Description
Right now, if many Os return errors to a B resulting in B sending out additional discovery requests, the B could potentially send out a lot of discovery requests that repeatedly result in errors that cause the B to end up sending tons of HTTP requests. In this scenario, if particular Os continue to return errors, it might make sense to add a backoff/rate limit strategy to reduce the work that B has to do if the Os are consistently returning errors.
Contributor guide
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 locating the discovery-request path in the Go repository and trace how errors trigger additional requests. Define the backoff or rate-limit behavior for consistently failing Os, then verify that repeated errors no longer cause unbounded HTTP requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100