We have three replicas, so we just performed md5sum on all of them in order
to find the correct ones, then we deleted the bad file and ran pg repair.
On 15 Feb 2016 10:42 a.m., "Zoltan Arnold Nagy"
wrote:
> Hi Bryan,
>
> You were right: we’ve modified our PG weights a little (from 1 to around
> 0
Zoltan,
It's good to hear that you were able to get the PGs stuck in 'remapped'
back into a 'clean' state. Based on your response I'm guessing that your
failure domains (node, rack, or maybe row) are too close (or equal) to
your replica size.
For example if your cluster looks like this:
3 repli
Hi Bryan,
You were right: we’ve modified our PG weights a little (from 1 to around 0.85
on some OSDs) and once I’ve changed them back to 1, the remapped PGs and
misplaced objects were gone.
So thank you for the tip.
For the inconsistent ones and scrub errors, I’m a little wary to use pg repair