tsdb creation supports fingerprint overrides #6178
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.
This PR ensures we use the correct (without tenant label) fingerprints in TSDB creation ordering.
This is a tricky one. I noticed crashes during TSDB WAL replays due to out of order index entries. This is because we add a
__loki_tenant__
label to TSDB for pre-compacted indices. Previously, we were sorting series by the label-hashes which included the tenant label, which exposed us to ordering issues. Now, we use the correct fingerprint without the synthetic label.ref #5428