Retry RESOURCE_EXHAUSTED only if the server can recover #2480
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
tigrannajaryan
approved these changes
Apr 8, 2022
SergeyKanzhelev
approved these changes
Apr 8, 2022
arminru
approved these changes
Apr 11, 2022
|
@svrakitin please resolve the conflicts. |
reyang
approved these changes
Apr 13, 2022
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.
Recommend clients to retry on
RESOURCE_EXHAUSTEDonly if the server can recover. The server can indicate this by signaling backpressure (by includingRetryInfointo response).See: open-telemetry/opentelemetry-collector#5147 (comment)
I might need help with exact wording here to stay consistent with the rest of the spec.