Generic backoff timer to limit any behavior, currently log messages #3912
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What's being changed:
Abstracted from resource scans, generalized, and improved. Also applied to flush cycle readonly warning, since 1 log per second, per bucket are a lot of messages.
The constructor takes variadic arg of
time.Duration
, sorts it, and each iteration of interval-increase will take the next duration. Once the duration slice is exhausted, an interval of the longest duration is used for the remaining lifetime of the timer.Review checklist