Poller autoscaler: add backoff on ResourceExhausted errors#1110
Merged
Poller autoscaler: add backoff on ResourceExhausted errors#1110
Conversation
chris-olszewski
approved these changes
Feb 12, 2026
Sushisource
approved these changes
Feb 12, 2026
Member
Sushisource
left a comment
Sushisource
left a comment
There was a problem hiding this comment.
Awesome, thanks James, just one small suggestion.
This was referenced Feb 19, 2026
Bump Temporalio.Extensions.DiagnosticSource from 1.9.0 to 1.11.1
InfinityFlowApp/aspire-temporal#281
Closed
Closed
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 was changed
Why?
Previously, when autoscaling pollers would hit
ResourceExhaustederrors (e.g., namespace rate limits), they were retrying immediately with no backoff, creating a sustained hot loop that could generate at extremely high rate (over 60Kreq/seq in local simulations, but more realistically a few hundreds assuming normal network capacity).This PR adds exponential backoff logic to the poller autoscaller, with the same configuration as is applied by default by the client on
ResourceExhaustederrors, i.e.: (1s initial, 10s max, 2x multiplier).How was it tested?