Skip to content
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

Merged

Conversation

xinlian12
Copy link
Member

@xinlian12 xinlian12 commented Mar 16, 2022

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:

  • The pull request does not introduce [breaking changes]
  • CHANGELOG is updated for new features, bug fixes or other significant changes.
  • I have read the contribution guidelines.

General Guidelines and Best Practices

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

  • Pull request includes test coverage for the included changes.

@azure-sdk
Copy link
Collaborator

API changes have been detected in com.azure:azure-cosmos. You can review API changes here

API changes

+         @Beta public boolean isSuppressInitError() 
+         @Beta public ThroughputControlGroupConfigBuilder setSuppressInitError(boolean suppressInitError) 
-             V4_27_0;
+             V4_27_0,
+             V4_28_0;

@azure-sdk
Copy link
Collaborator

API changes have been detected in com.azure:azure-cosmos. You can review API changes here

API changes

+         @Beta public boolean isContinueOnInitError() 
+         @Beta public ThroughputControlGroupConfigBuilder setContinueOnInitError(boolean continueOnInitError) 
-             V4_27_0;
+             V4_27_0,
+             V4_28_0;

@check-enforcer
Copy link

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:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

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:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run java - [service] - ci

@@ -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) {
Copy link
Member

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?

Copy link
Member

@FabianMeiswinkel FabianMeiswinkel left a 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

@azure-sdk
Copy link
Collaborator

API changes have been detected in com.azure:azure-cosmos. You can review API changes here

API changes

+         @Beta public boolean isContinueOnInitError() 
+         @Beta public ThroughputControlGroupConfigBuilder setContinueOnInitError(boolean continueOnInitError) 
-             V4_27_0;
+             V4_27_0,
+             V4_28_0;

@azure-sdk
Copy link
Collaborator

API changes have been detected in com.azure:azure-cosmos. You can review API changes here

@xinlian12
Copy link
Member Author

Add changeLog after the current deployment change finish, else merge conflicts for the changelog

Copy link
Member

@kushagraThapar kushagraThapar left a 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.

@azure-sdk
Copy link
Collaborator

API change check for com.azure:azure-cosmos

API changes have been detected in com.azure:azure-cosmos. You can review API changes here

@xinlian12
Copy link
Member Author

/azp run java - cosmos - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@xinlian12 xinlian12 merged commit 2dab32d into Azure:main Apr 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants