Skip to content

release-21.2: multitenant: exempt sqlliveness operations from cost control#71123

Merged
RaduBerinde merged 1 commit intorelease-21.2from
blathers/backport-release-21.2-71038
Oct 7, 2021
Merged

release-21.2: multitenant: exempt sqlliveness operations from cost control#71123
RaduBerinde merged 1 commit intorelease-21.2from
blathers/backport-release-21.2-71038

Conversation

@blathers-crl
Copy link
Copy Markdown

@blathers-crl blathers-crl bot commented Oct 5, 2021

Backport 1/1 commits from #71038 on behalf of @RaduBerinde.

/cc @cockroachdb/release


This change adds infrastructure to allow certain contexts to be exempt
from cost control (meaning that we don't throttle or charge for them)
and uses it to exempt sqlliveness operations - most importantly, the
heartbeats, which are time-sensitive and necessary to keep the SQL
session alive.

Release note: None

Release justification: Necessary fix for the distributed rate limiting
functionality, which is vital for the upcoming Serverless MVP release.
It allows CRDB to throttle clusters that have run out of free or paid
request units (which measure CPU and I/O usage). This functionality is
only enabled in multi-tenant scenarios and should have no impact on
our dedicated customers.

Informs #68479.


Release justification:

This change adds infrastructure to allow certain contexts to be exempt
from cost control (meaning that we don't throttle or charge for them)
and uses it to exempt sqlliveness operations - most importantly, the
heartbeats, which are time-sensitive and necessary to keep the SQL
session alive.

Release note: None

Release justification: Necessary fix for the distributed rate limiting
functionality, which is vital for the upcoming Serverless MVP release.
It allows CRDB to throttle clusters that have run out of free or paid
request units (which measure CPU and I/O usage). This functionality is
only enabled in multi-tenant scenarios and should have no impact on
our dedicated customers.
@blathers-crl blathers-crl bot requested a review from a team as a code owner October 5, 2021 04:11
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-21.2-71038 branch from d6ee25e to 26a5da3 Compare October 5, 2021 04:11
@blathers-crl
Copy link
Copy Markdown
Author

blathers-crl bot commented Oct 5, 2021

Thanks for opening a backport.

Please check the backport criteria before merging:

  • Patches should only be created for serious issues.
  • Patches should not break backwards-compatibility.
  • Patches should change as little code as possible.
  • Patches should not change on-disk formats or node communication protocols.
  • Patches should not add new functionality.
  • Patches must not add, edit, or otherwise modify cluster versions; or add version gates.
If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.
  • There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
  • The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
  • New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters.
  • The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.

Add a brief release justification to the body of your PR to justify this backport.

Some other things to consider:

  • What did we do to ensure that a user that doesn’t know & care about this backport, has no idea that it happened?
  • Will this work in a cluster of mixed patch versions? Did we test that?
  • If a user upgrades a patch version, uses this feature, and then downgrades, what happens?

@cockroach-teamcity
Copy link
Copy Markdown
Member

This change is Reviewable

Copy link
Copy Markdown
Contributor

@andy-kimball andy-kimball left a comment

Choose a reason for hiding this comment

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

:lgtm:

Reviewable status: :shipit: complete! 1 of 0 LGTMs obtained (waiting on @ajwerner and @knz)

@RaduBerinde RaduBerinde merged commit 16f9040 into release-21.2 Oct 7, 2021
@rafiss rafiss deleted the blathers/backport-release-21.2-71038 branch November 22, 2021 06:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants