- 
                Notifications
    You must be signed in to change notification settings 
- Fork 522
Hedging: Fixes Concurrency Issue #5189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hedging: Fixes Concurrency Issue #5189
Conversation
| I thought your previous PR | 
| 
 Context: In an offline discussion we decided to only take some of the changes with that PR and create a new one. | 
        
          
                ...soft.Azure.Cosmos/src/Routing/AvailabilityStrategy/CrossRegionHedgingAvailabilityStrategy.cs
              
                Outdated
          
            Show resolved
            Hide resolved
        
              
          
                ...soft.Azure.Cosmos/src/Routing/AvailabilityStrategy/CrossRegionHedgingAvailabilityStrategy.cs
              
                Outdated
          
            Show resolved
            Hide resolved
        
              
          
                ...soft.Azure.Cosmos/src/Routing/AvailabilityStrategy/CrossRegionHedgingAvailabilityStrategy.cs
          
            Show resolved
            Hide resolved
        
      There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - Thanks!
        cd38683
      
    There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Pull Request Template
Description
This pull request refactors the
CrossRegionHedgingAvailabilityStrategyclass in the Azure Cosmos SDK to fix a rare concurrency issue regarding session tokens and improve diagnostics for improved debugging.. It also updates related tests to align with the changes. The most important changes include replacing theResponse Regiondiagnostic with a newHedge Configdiagnostic, modifying theHedgingResponseclass, and updating test cases to validate the new behavior. theResponse Regionfield can sometimes be inaccurate with internal cross regional retries so it has been removed. To find the response region, you can look at the existing store response to see where the response came from.Type of change
Please delete options that are not relevant.
Closing issues
To automatically close an issue: closes #IssueNumber