pkg/ingester: added sync period flags #1438
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
-ingester.sync-period
can be used to tell ingesters to cut chunks early (before they are full) to synchronize ingesters so that they put the same data into the new chunks. If they do, they generate fully equal chunks and then they don't need to store them.To avoid very small chunks, additional parameter is added:
-ingester.sync-min-utilization
. When set to eg. 0.5, chunk must be at least 50% full (utilization) in order to be cut early for sync purposes.To avoid all chunks to be cut at the same time, series fingerprint is used as an offset to sync period. We need some value that all ingesters know about and can use, and although series fingerprints can be remapped on ingesters differently, they are good enough.
Based on Bryan Boreham's work in Cortex.
Signed-off-by: Peter Štibraný peter.stibrany@grafana.com
Special notes for your reviewer:
Checklist