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

chore: Client change for using request priority to enable flow control #1900

Closed

Conversation

kongweihan
Copy link
Contributor

In this stage, client needs to do 3 things:

  1. Always create flow control callable regardless of client flag
  2. Make sure the entire callable behave like no-op if RateLimitInfo is not present.
  3. Make sure client runs flow control as long as RateLimitInfo is present, regardless of client flag.

Meanwhile, setting client flag would still set the feature flag.

On server side, we'll compute and return RateLimitInfo if AFE sees priority is low.

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

  • Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
  • Ensure the tests and linter pass
  • Code coverage does not decrease (if any source code was changed)
  • Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> ☕️

If you write sample code, please follow the samples format.

@product-auto-label product-auto-label bot added size: s Pull request size is small. api: bigtable Issues related to the googleapis/java-bigtable API. labels Sep 7, 2023
@kongweihan kongweihan force-pushed the kongwh-request-priority-patch-1 branch 2 times, most recently from ec8d677 to f29295e Compare September 11, 2023 14:33
@kongweihan kongweihan marked this pull request as ready for review September 11, 2023 14:36
@kongweihan kongweihan requested a review from a team as a code owner September 11, 2023 14:36
@kongweihan kongweihan force-pushed the kongwh-request-priority-patch-1 branch from f29295e to 0090371 Compare September 11, 2023 14:37
@product-auto-label product-auto-label bot added size: m Pull request size is medium. and removed size: s Pull request size is small. labels Sep 11, 2023
In this stage, client needs to do 3 things:
1. Always create flow control callable regardless of client flag
2. Make sure the entire callable behave like no-op if RateLimitInfo is not present.
3. Make sure client runs flow control as long as RateLimitInfo is present, regardless of client flag.

Meanwhile, setting client flag would still set the feature flag.

On server side, we'll compute and return RateLimitInfo if server side sees priority is low.
@kongweihan kongweihan force-pushed the kongwh-request-priority-patch-1 branch from 0090371 to 761bab7 Compare September 11, 2023 15:02
…ty-patch-1

Change-Id: Ib9f2520b70cc570d76dbe04e5ecd1ae4a28ac8c5
Change-Id: I721ad64ce49b0310eb44d86e3b171ab2bef46437
@igorbernstein2 igorbernstein2 changed the title Client change for using request priority to enable flow control chore: Client change for using request priority to enable flow control Sep 11, 2023
Copy link
Contributor

@kolea2 kolea2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change-Id: Ibda6daed72f0f267ad741836701848f33c2d5377
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: bigtable Issues related to the googleapis/java-bigtable API. size: m Pull request size is medium.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants