Repository navigation
Conversation
Signed-off-by: Kuromesi <blackfacepan@163.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
This branch has not been deployed
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.
Overload rejection, early stream closure, and some other ADS failures can cause clients to reconnect too aggressively or retain a large backoff after a successful configuration exchange. Large groups of clients also retry Sandbox restoration at the same fixed interval.
Apply exponential backoff consistently, use a nominal one-second minimum for
ResourceExhaustedreturned during either stream establishment or streaming, and add ±20% jitter with an actual delay capped at 15 seconds. Reset accumulated backoff after an accepted response and retain fast retries for healthy stream completion. Jitter automatic Sandbox restoration retries from five seconds to four–six seconds; the per-attempt 30-second preparation timeout is unchanged.Add TLS/gRPC regression tests covering overload, early EOF, and backoff reset after an accepted response.
Validation:
my-ecs(the filtered sets overlap).Test reports and generated load-test artifacts are excluded from this PR.