Skip to content

Record block data size in meta #515

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

Merged
merged 6 commits into from
Feb 9, 2021
Merged

Conversation

mdisibio
Copy link
Contributor

@mdisibio mdisibio commented Feb 8, 2021

What this PR does:
This PR adds a new field to the block meta for the final data file size, and support for this and other recent fields to the tempo-cli. This PR is a precursor to switching compaction over to a target file size instead of target trace count.

Which issue(s) this PR fixes:
n/a

Checklist

  • Tests updated
  • Documentation added
  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]
Copy link
Collaborator

@joe-elliott joe-elliott left a comment

Choose a reason for hiding this comment

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

An appender is used by both the compactor and complete blocks. It already does some record keeping w/r to the amount of data that has been appended. If we want to track "totalSize" does it make sense to just put the logic there?

Echo @annanay25 's question about whether or not we need both. the compressed size seems like enough to me. If we are just interested in compression ratio we may want to consider metricing it. I know Loki does that.

@mdisibio mdisibio changed the title WIP - Record block data/file sizes in meta Feb 9, 2021
@mdisibio mdisibio merged commit 734bbf2 into grafana:master Feb 9, 2021
@mdisibio mdisibio deleted the meta-sizes branch May 27, 2021 13:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants