-
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
AllowRequestContinueForThroughputControlInitError #27702
AllowRequestContinueForThroughputControlInitError #27702
Conversation
...azure/cosmos/implementation/throughputControl/ContainerThroughputControlGroupProperties.java
Outdated
Show resolved
Hide resolved
.../src/main/java/com/azure/cosmos/implementation/throughputControl/ThroughputControlStore.java
Outdated
Show resolved
Hide resolved
API changes have been detected in API changes + @Beta public boolean isSuppressInitError()
+ @Beta public ThroughputControlGroupConfigBuilder setSuppressInitError(boolean suppressInitError)
- V4_27_0;
+ V4_27_0,
+ V4_28_0; |
API changes have been detected in API changes + @Beta public boolean isContinueOnInitError()
+ @Beta public ThroughputControlGroupConfigBuilder setContinueOnInitError(boolean continueOnInitError)
- V4_27_0;
+ V4_27_0,
+ V4_28_0; |
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/ThroughputControlGroupConfig.java
Show resolved
Hide resolved
...azure/cosmos/implementation/throughputControl/ContainerThroughputControlGroupProperties.java
Show resolved
Hide resolved
...azure/cosmos/implementation/throughputControl/ContainerThroughputControlGroupProperties.java
Outdated
Show resolved
Hide resolved
@@ -159,9 +147,37 @@ public void enableThroughputControlGroup(ThroughputControlGroupInternal group) { | |||
// We will handle the first scenario by creating a new container controller, | |||
// while fall back to original request Mono for the second scenario. | |||
return this.updateControllerAndRetry(collectionNameLink, request, originalRequestMono); | |||
}) | |||
.onErrorResume(throwable -> { | |||
if (throwable instanceof ThroughputControlInitializationException) { |
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.
Shouldn't we unwrap this throwable as this is coming from reactor?
.../src/main/java/com/azure/cosmos/implementation/throughputControl/ThroughputControlStore.java
Outdated
Show resolved
Hide resolved
...com/azure/cosmos/implementation/throughputControl/config/ThroughputControlGroupInternal.java
Outdated
Show resolved
Hide resolved
...azure/cosmos/implementation/throughputControl/ContainerThroughputControlGroupProperties.java
Outdated
Show resolved
Hide resolved
...os/implementation/throughputControl/exceptions/ThroughputControlInitializationException.java
Outdated
Show resolved
Hide resolved
sdk/cosmos/azure-cosmos/src/main/java/com/azure/cosmos/ThroughputControlGroupConfigBuilder.java
Outdated
Show resolved
Hide resolved
...lementation/throughputControl/controller/group/global/ThroughputControlContainerManager.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.
LGTM except for few minor comments
…hub.com/xinlian12/azure-sdk-for-java into allowSuppressThroughputControlInitError
API changes have been detected in API changes + @Beta public boolean isContinueOnInitError()
+ @Beta public ThroughputControlGroupConfigBuilder setContinueOnInitError(boolean continueOnInitError)
- V4_27_0;
+ V4_27_0,
+ V4_28_0; |
API changes have been detected in |
Add changeLog after the current deployment change finish, else merge conflicts for the changelog |
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.
Thanks @xinlian12 - looks great to me.
API change check for API changes have been detected in |
/azp run java - cosmos - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
Description
Issue: #20020
Summary
Currently, if throughput control controller initialized failed due to any reason, the request using throughput control will also fail. This enables the capability for customer to opt out this default behavior.
If continueOnInitError = true, request will fallback to original request flow if throughput control controller failed on initialization.
If continueOnInitError = false (also the default value), request will fail if throughput control controller failed on initialization.
How to enable continueOnInitError:
new ThroughputControlGroupConfigBuilder()
.setContinueOnInitError(true)
So the request flow:
request1 -> throughputcontrolStore -> initialize all underlying controllers -> failed -> fallbackOnInitError ? -> yes, fallback to original request flow, no fail the request
...
requestN -> throughputcontrolStore -> initialize all underlying controllers -> failed -> fallbackOnInitError ? -> yes, fallback to original request flow, no fail the request
All SDK Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines