Hm I'm not so sure, because we did have a disk outage indeed.
When we added many new disks, 50% of objects were misplaced.
Then the disk failed and ~2% of objects were degraded.
The recovery went on fine, but I would expect that fixing the degraded objects
should have a priority over data
migrati
I think that all the misplaced PGs that are in the queue that get
writes _while_ waiting for backfill will get the "degraded" status,
meaning that before they were just on the wrong place, now they are on
the wrong place, AND the newly made PG they should backfill into will
get an old dump made fir
Hello!
My cluster currently has this health state:
2018-10-31 21:20:13.694633 mon.lol [WRN] Health check update:
39010709/192173470 objects misplaced (20.300%)
(OBJECT_MISPLACED)
2018-10-31 21:20:13.694684 mon.lol [WRN] Health check update: Degraded data
redundancy: 1624786/192173470 objects
de
