Poller autoscaler: further refinement of backoff on grpc errors#1111
Merged
Poller autoscaler: further refinement of backoff on grpc errors#1111
Conversation
Sushisource
approved these changes
Feb 13, 2026
chris-olszewski
approved these changes
Feb 17, 2026
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
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
ResourceExhaustederrors in the case where we've never seen a scaling decision from the server.Why?
In #1110, we added exponential backoff logic to the poller autoscaller. We however only applied the backoff if we had previously received a scaling decision from the server, and only for
ResourceExhaustederrors.How was it tested?