-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
compact: no-compact-mark.json ignored #5603
Comments
Hello 👋 Looks like there was no activity on this issue for the last two months. |
How to reproduce the issue
Expected result: Actual result:
Same error occurs with deletion-mark.json @yeya24 can you, please, confirm the expected result? or was there different logic in mind? I can dig deeper and propose a fix, so that thanos compact will ignore marked blocks. |
As I undertood from #3409 blocks with no-compact-mark.json should not be compacted. It is so, but the check is in the planner. |
I can't repro this locally with neither the OP's instructions:
Nor these ones. I believe that this might be the actual fix. |
@GiedriusS I've just reproduced the bug on main branch with your last commit "compact: atomically replace no compact marked map (#6319)" the steps are still actual. so the bug still exists. |
I wonder if this is still an issue. @GiedriusS @xBazilio Do we know if we can resolve this issue or it is still a problem |
I can confirm that this is NOT an issue any more. |
Thanos, Prometheus and Golang version used:
quay.io/thanos/thanos:v0.25.1
Object Storage Provider:
S3
What happened:
What you expected to happen:
I've marked both blocks to skip compaction, so I'd expect compact to not try to compact them.
How to reproduce it (as minimally and precisely as possible):
I guess to reproduce you'd have to create a corrupt block. In my case prometheus did this for me. ;) If you wanted to do it, I guess you could just pick a block and change some random characters, that would probably cause a checksum mismatch.
Step two would be to turn on compact and confirm it halts on the block.
Step 3 would be to add the no-compact-mark and bounce compact.
Full logs to relevant components:
Anything else we need to know:
I found a couple similar issues:
However, both of those specifically relate to no-compact being ignored when index size exceeds 64GiB. In my case the index size is nominal, but no-compact is still being ignored.
The text was updated successfully, but these errors were encountered: