MimirCompactorHasNotSuccessfullyRunCompaction | checksum mismatch #7614
-
Describe the bugMimir reports the following alarm MimirCompactorHasNotSuccessfullyRunCompaction in the logs of mimir I see the following: To ReproduceSteps to reproduce the behavior: I tried to unify the data from two mimir clusters into one and copied blocks to a single s3 bucket. Expected behaviorResolve issue of checksum mismatch Environment
Additional Context |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Block is now corrupted, and cannot be compacted anymore. You can use
|
Beta Was this translation helpful? Give feedback.
Block is now corrupted, and cannot be compacted anymore. You can use
markblocks
tool from Mimir repository to mark block for non-compaction. If you are running Mimir 2.11, it has a feature to mark corrupted blocks for non-compaction automatically.