-
Notifications
You must be signed in to change notification settings - Fork 494
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
Control Plane Hot Path: Adds more aggressive timeout and retry logic #1954
Conversation
…for control plane hot paths.
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.
New timeouts for query plan need to be approved by query team.
….com/Azure/azure-cosmos-dotnet-v3 into users/jawilley/http/transientRetries
….com/Azure/azure-cosmos-dotnet-v3 into users/jawilley/http/transientRetries
…/transientRetries
….com/Azure/azure-cosmos-dotnet-v3 into users/jawilley/http/transientRetries
…/transientRetries
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 besides a couple of small comments
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, just left some nits in case it makes sense to apply
Microsoft.Azure.Cosmos/src/HttpClient/HttpTimeoutPolicyControlPlaneHotPath.cs
Outdated
Show resolved
Hide resolved
Microsoft.Azure.Cosmos/src/HttpClient/HttpTimeoutPolicyControlPlaneRead.cs
Outdated
Show resolved
Hide resolved
…/transientRetries
….com/Azure/azure-cosmos-dotnet-v3 into users/jawilley/http/transientRetries
PR #1954 only did retries on get operations. Get query plan is a post causing it to not do the faster retries. This adds explicit test to verify the behavior and to prevent future regression. The diagnostics was updated to always include the retry policy to help trouble shoot issues in the future.
Closing due to in-activity, pease feel free to re-open. |
Pull Request Template
Description
Non-hotpath (Account information)
Read:
5 second timeout (No delay on first retry)
10 second timeout
20 second timeout
Hotpath (QueryPlan, partition key ranges, address refresh)
Read retry in the same region. Does not impact region failover:
.5 second timeout (No delay on first retry)
5 second timeout
10 second timeout
All other operations use the current default of 65 seconds.
Tests are still in progress.
Type of change
Please delete options that are not relevant.
Closing issues
closes #1872 #1912