Refine the retry logic
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 131
- Forks
- 10
- Avg merge
- 2h 5m
- Merged PRs (30d)
- 6
Description
What feature do you want to see added?
Currently we are using a very simple 5s polling. While this is simple, this also may cause DDOS if a lot of plugins start polling the server during an outage.
It'd be nice to make this a bit smarter and recognize "normal operations" from "errors" so that errors could use exponential backoff.
See also https://github.com/GradleUp/nmcp/issues/86
Upstream changes
No response
Are you interested in contributing this feature?
No response
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 issue 86 and locating the implementation of the current 5-second polling behavior. Determine how normal operations are distinguished from errors, then define and test completion criteria for exponential backoff during outages without slowing normal polling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100