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

kvserver: expose LSM snapshot storage-engine timeseries metrics #100518

Merged
merged 1 commit into from
Apr 6, 2023

Conversation

jbowens
Copy link
Collaborator

@jbowens jbowens commented Apr 3, 2023

Expose two new storage-engine metrics that provide visibility into LSM snapshots. These two new metrics record cumulative count and size of obsolete keys written to sstables during flushes and compactions.

Epic: None
Release note (ops change): Expose two new timeseries metrics storage.compactions.keys.pinned.count and
storage.compactions.keys.pinned.bytes providing some observability into the volume of keys preserved by open LSM snapshots.

Informs cockroachdb/pebble#1204.

@jbowens jbowens added the backport-23.1.x Flags PRs that need to be backported to 23.1 label Apr 3, 2023
@jbowens jbowens requested review from a team and RaduBerinde April 3, 2023 20:53
@blathers-crl
Copy link

blathers-crl bot commented Apr 3, 2023

It looks like your PR touches production code but doesn't add or edit any test code. Did you consider adding tests to your PR?

🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.

@cockroach-teamcity
Copy link
Member

This change is Reviewable

@jbowens jbowens marked this pull request as ready for review April 3, 2023 21:35
@jbowens jbowens requested a review from a team April 3, 2023 21:35
@jbowens jbowens requested a review from a team as a code owner April 3, 2023 21:35
Copy link
Member

@RaduBerinde RaduBerinde 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

Expose two new storage-engine metrics that provide visibility into LSM
snapshots. These two new metrics record cumulative count and size of obsolete
keys written to sstables during flushes and compactions.

Epic: None
Release note (ops change): Expose two new timeseries metrics
`storage.compactions.keys.pinned.count` and
`storage.compactions.keys.pinned.bytes` providing some observability into the
volume of keys preserved by open LSM snapshots.

Informs cockroachdb/pebble#1204.
Copy link
Member

@RaduBerinde RaduBerinde left a comment

Choose a reason for hiding this comment

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

Reviewed 2 of 2 files at r2, all commit messages.
Reviewable status: :shipit: complete! 0 of 0 LGTMs obtained (and 1 stale) (waiting on @jbowens)

@jbowens
Copy link
Collaborator Author

jbowens commented Apr 6, 2023

TFTR!

bors r=RaduBerinde

@jbowens
Copy link
Collaborator Author

jbowens commented Apr 6, 2023

bors r=RaduBerinde

@craig
Copy link
Contributor

craig bot commented Apr 6, 2023

Build succeeded:

@craig craig bot merged commit 8e532bb into cockroachdb:master Apr 6, 2023
@blathers-crl
Copy link

blathers-crl bot commented Apr 6, 2023

Encountered an error creating backports. Some common things that can go wrong:

  1. The backport branch might have already existed.
  2. There was a merge conflict.
  3. The backport branch contained merge commits.

You might need to create your backport manually using the backport tool.


error creating merge commit from 6847cfd to blathers/backport-release-23.1-100518: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict []

you may need to manually resolve merge conflicts with the backport tool.

Backport to branch 23.1.x failed. See errors above.


🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-23.1.x Flags PRs that need to be backported to 23.1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants