Skip to content

release-21.2: multitenant: add pgwire bytes component to tenant cost#70954

Merged
RaduBerinde merged 1 commit intocockroachdb:release-21.2from
RaduBerinde:backport21.2-70877
Oct 2, 2021
Merged

release-21.2: multitenant: add pgwire bytes component to tenant cost#70954
RaduBerinde merged 1 commit intocockroachdb:release-21.2from
RaduBerinde:backport21.2-70877

Conversation

@RaduBerinde
Copy link
Copy Markdown
Member

Backport 1/1 commits from #70877.

/cc @cockroachdb/release


This commit adds accounting for the total number of bytes transferred
through pgwire.

We currently just passively record the usage, similar to CPU. In the
future, we will consider throttling the sending of data to the client.

The tenant cost model setting is a preliminary guess, we are in the
process of revisiting all the values.

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.

This commit adds accounting for the total number of bytes transferred
through pgwire.

We currently just passively record the usage, similar to CPU. In the
future, we will consider throttling the sending of data to the client.

The tenant cost model setting is a preliminary guess, we are in the
process of revisiting all the values.

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.
@RaduBerinde RaduBerinde requested a review from a team as a code owner September 30, 2021 20:58
@blathers-crl
Copy link
Copy Markdown

blathers-crl bot commented Sep 30, 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)

Copy link
Copy Markdown
Contributor

@ajwerner ajwerner left a comment

Choose a reason for hiding this comment

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

:lgtm:

Reviewed 10 of 24 files at r1, all commit messages.
Reviewable status: :shipit: complete! 2 of 0 LGTMs obtained (waiting on @ajwerner)

@RaduBerinde RaduBerinde merged commit 0ae364c into cockroachdb:release-21.2 Oct 2, 2021
@RaduBerinde RaduBerinde deleted the backport21.2-70877 branch October 2, 2021 15:02
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