Add a max retry time for ExponentialBackoffRetryPolicy
- Dominant language
- Java
- Stars
- 6.1k
- Forks
- 1.5k
- Avg merge
- 2d 55m
- Merged PRs (30d)
- 182
Description
https://github.com/apache/pinot/pull/10804. Currently the ExponentialBackoffRetryPolicy is not intuitive to use, e.g. with a (maxNumAttempts, initialDelayMs, delayScaleFactor) combination it is hard to see what's the maximum retry time, and this could potentially lead to resource held up for unexpected time. It would be ideal if we can put an upper bound on the retry time.
Contributor guide
Research direction
Start by reading ExponentialBackoffRetryPolicy and the linked pull request 10804 to understand the current retry parameters and proposed direction. Define how a maximum retry time should interact with the existing attempt, delay, and scale-factor settings, then verify the behavior against the intended upper bound.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100