-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Session timeout 404/1002 HA fixes #18594
Session timeout 404/1002 HA fixes #18594
Conversation
This pull request is protected by Check Enforcer. What is Check Enforcer?Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass. Why am I getting this message?You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged. What should I do now?If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows: What if I am onboarding a new service?Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment: |
sdk/cosmos/azure-cosmos/src/main/java/com/azure/cosmos/implementation/ClientRetryPolicy.java
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.
great work @simplynaveen20 thanks for leading to improve the fail over scenarios.
a few minor comments.
...azure-cosmos/src/test/java/com/azure/cosmos/implementation/SessionNotAvailableRetryTest.java
Show resolved
Hide resolved
...azure-cosmos/src/test/java/com/azure/cosmos/implementation/SessionNotAvailableRetryTest.java
Outdated
Show resolved
Hide resolved
...azure-cosmos/src/test/java/com/azure/cosmos/implementation/SessionNotAvailableRetryTest.java
Outdated
Show resolved
Hide resolved
...azure-cosmos/src/test/java/com/azure/cosmos/implementation/SessionNotAvailableRetryTest.java
Outdated
Show resolved
Hide resolved
return ObservableHelper.inlineIfPossibleAsObs( | ||
() -> { | ||
if(finalRetryPolicy != null) { |
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.
great catch. thanks
...azure-cosmos/src/test/java/com/azure/cosmos/implementation/SessionNotAvailableRetryTest.java
Outdated
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 - except for Mo's comments about reflection usage in InternalObjectNode. once those are addressed I am good.
…improving code readablity
/azp run java - cosmos - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run java - cosmos - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Thank you @simplynaveen20
LGTM.
As we are planning to do a hotfix release on Friday, before merging this PR please check with @kushagraThapar whether to include this hotfix in the bugfix release or not.
as we may want to keep this change in the master branch run a few CTL before releasing it to public.
@@ -366,6 +366,27 @@ Licensed under the MIT License. | |||
</plugins> | |||
</build> | |||
</profile> | |||
<profile> | |||
<!-- integration tests, requires Cosmos DB endpoint with multi region support --> | |||
<id>multi-region</id> |
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.
some of the CIs provide multi-region account to the existing test group.
Why do we need this additional test group?
also is there a specific consistency configured in the CI for the test group?
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.
We don't have any group which runs only multi-region single master. My test need that case explicitly
/azp run java - cosmos - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run java - cosmos - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run java - cosmos - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run java - cosmos - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run java - cosmos - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
tests.yml LGTM |
Review request for Microsoft.ContainerService to add version 2022-03-01 (Azure#18686) * Adds base for updating Microsoft.ContainerService from version stable/2022-02-01 to version 2022-03-01 * Updates readme * Updates API version in new specs and examples * Update readmes for the 2022-03-01 dev branch of container service (Azure#18357) * update readme * update sdk readmes * feat: add ManagedCluster StorageProfile in 0301 (Azure#18594) Signed-off-by: Ji An Liu <[email protected]> * Replace common type definitions with references since 2022-03-01 for Microsoft.ContainerService (Azure#18568) * replace Resource * replacing systemData * replace parameters * fix: replace Resource with TrackedResource * replace track2 with python Co-authored-by: Ji'an Liu <[email protected]>
This PR contains below fixes.
Regional retry is not working in query Query Session time out 404/1002, we are only retrying in same region #18498
Requests are retrying twice on same region Session time out 404/100, requests are retrying twice on same region #18499
Scenario - User's multi master region preferred list (A,B,C) before this fix ,call were going A, A, B, C. It should be A, B, C, A
Single master will behave the same as before i.e. Preferred region, Master region, Preferred region
Small improvement in read item code , where retryPolicy.onBeforeSendRequest(request) were getting called twice
unnecessary, creating confusing during debugging client retry policy