[Membership] Addressing recovery from contention on membership writes #9376
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
rkargMsft
changed the title
rkargMsft
changed the title
dmorganMsft
approved these changes
Mar 21, 2025
This alleviates overloading clustering storage when it is performing slower than normal request rates.
This helps avoid contention and increases the chance that one silo will perform the operation.
ReubenBond
approved these changes
Mar 21, 2025
|
@rkargMsft if my changes look good to you, I'm ready to merge. |
|
@ReubenBond LGTM |
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.
This alleviates overloading clustering storage when it is performing slower than normal request rates.
Microsoft Reviewers: Open in CodeFlow
This appears to be the only two places with writes that would have retries when encountering slow membership backends that doesn't have exponential backoffs.