-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
allow configuring a target chunk size in compressed bytes #1406
Conversation
Signed-off-by: Edward Welch <edward.welch@grafana.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! This is just a quick first pass.
docs/configuration/README.md
Outdated
@@ -267,8 +267,16 @@ The `ingester_config` block configures Ingesters. | |||
# period as long as they receieve no further activity. | |||
[chunk_idle_period: <duration> | default = 30m] | |||
|
|||
# The maximum size in bytes a chunk can be before it should be flushed. | |||
# The maximum _uncompressed_ size in bytes of a chunk block, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this is 100% accurate: almost all blocks are going to end up being greater than this size. This is more like the cuttoff point for when an uncompressed block should be compressed.
Do you think it's worth explaining that in the docs?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah agree, will reword this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rfratto reworded, let me know what you think
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, this is more clear. Thanks!
Signed-off-by: Edward Welch <edward.welch@grafana.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Limiting chunks query start time with config
Need to figure out still what to do with the error if you fail to cut a chunk...
Signed-off-by: Edward Welch edward.welch@grafana.com