-
Notifications
You must be signed in to change notification settings - Fork 816
compaction halt when "overlapping sources detected for plan" #5806
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
Comments
Can you guys help take a look? |
The error is Based on log, all 5 blocks in this compaction plan are having min time: 1699833600000, max time: 1699840800000. Probably they are having some common source blocks. In this case, it is considered as overlapping blocks. Here is the code doing this overlapping check: https://github.com/cortexproject/cortex/blob/master/vendor/github.com/thanos-io/thanos/pkg/compact/compact.go#L817 Could you please check meta.json of those blocks to validate if there are common source blocks among them? |
I had this exact problem today, it happened because 2 compactors were running against same s3 bucket for hours for the same user. |
Just want to double check. @friedrichg @AlexandreRoux, do you enable out of order samples feature? |
@yeya24 No, we don't. We also don't use shuffle sharding in compactors yet. (Cortex v1.16.0) |
I think this might happen if out of order samples is enabled because a single block might be compacted twice and got uploaded to the bucket. |
https://github.com/cortexproject/cortex/releases/tag/v1.17.0-rc.0 |
Describe the bug
Compactor halt compaction when hitting "overlapping sources detected for plan" level=error.
Since the plan will be retry indefinitely no new blocks will be compacted and only solution is to mark block for no-compact using thanos tools bucket.
Although we are using skip_blocks_with_out_of_order_chunks_enabled: true configuration, the block is not being marked as non-compact (possibly because root cause is something else than ooo chuncks).
To Reproduce
Unable to reproduce for now, simply noticed in our cortex environment.
Expected behavior
Unsure what expected behavior should be but a
skip_blocks_
should should be provided to continue compaction.Environment:
The text was updated successfully, but these errors were encountered: