-
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
Aggressive warm up duration fix and sync client warm up fix #36889
Conversation
…gressiveWarmUpDurationFix # Conflicts: # sdk/cosmos/azure-cosmos-tests/src/test/java/com/azure/cosmos/ProactiveConnectionManagementTest.java # sdk/cosmos/azure-cosmos/CHANGELOG.md
API change check API changes are not detected in this pull request. |
sdk/cosmos/azure-cosmos/src/main/java/com/azure/cosmos/CosmosAsyncClient.java
Outdated
Show resolved
Hide resolved
.withAggressiveWarmupDuration(Duration.ofMinutes(1000)) | ||
.withIsSystemPropertySetBeforeDirectConnectionConfig(false) | ||
.withIsSyncClient(false), | ||
new ProactiveConnectionManagementTestConfig() |
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.
since we introduced faultInjection on gateway, can we also add test cases where some errors during the warm up stage - for example collection read timed out etc. - can be in a different PR
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.
Tracking the work item here - #33088
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
…gressiveWarmUpDurationFix # Conflicts: # sdk/cosmos/azure-cosmos/CHANGELOG.md
/azp run java - cosmos - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/check-enforcer override |
This PR fixes the following bugs:
CosmosClient
orCosmosAsyncClient
would block until aggressive warm up duration elapses. This should not be the case when warm up can complete before this duration.CosmosClient
opened connections defensively even during the warmup phase. Defensive connection establishment should only happen after the client is built.