fix(storage): reduce Azure table retry pressure#10192
Merged
Merged
Conversation
ReubenBond
force-pushed
the
reminders-azure-backoff
branch
4 times, most recently
from
558b7b3 to
a83ca16
Compare
ReubenBond
changed the title
ReubenBond
changed the title
ReubenBond
force-pushed
the
reminders-azure-backoff
branch
2 times, most recently
from
7849b98 to
3020c65
Compare
Apply bounded outer-loop backoff for membership storage operations and delegate Azure Table per-operation retries to the Azure SDK exponential retry policy. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
ReubenBond
force-pushed
the
reminders-azure-backoff
branch
from
3020c65 to
f0a3244
Compare
This was referenced Jun 14, 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
1 participant
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.
Reduces Azure Table Storage pressure when many silos experience storage failures by applying bounded jittered backoff to the outer membership and reminder refresh loops, while delegating Azure Table per-operation retries to the Azure SDK exponential retry policy instead of layering an additional Orleans retry wrapper.
This keeps the retry layers separate: Orleans backs off periodic background loops after failures, and the Azure SDK handles per-call retries, server retry hints, and network timeouts.
Azure Table client retry defaults mirror Azure Storage SDK defaults where applicable, while keeping storage max retries at 5. References: