Adjust GetResource NotFound backoff #1810
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
t0yv0
commented
Nov 7, 2024
Does the PR have any schema changes?Looking good! No breaking changes found. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1810 +/- ##
==========================================
+ Coverage 45.67% 45.70% +0.02%
==========================================
Files 38 38
Lines 5916 5919 +3
==========================================
+ Hits 2702 2705 +3
Misses 2991 2991
Partials 223 223 ☔ View full report in Codecov by Sentry. |
corymhall
approved these changes
Nov 8, 2024
flostadler
approved these changes
Nov 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
GetResource NotFound backoff introduced in #1809 allowed long time wait periods up to 30 seconds. This change makes the max wait period 3 seconds at this is more appropriate for AWS eventual consistency propagation delays this backoff tries to compensate for.