Re: Kicking 'Remapped' PGs

[Paul Evans <paul@xxxxxxxxxxxx>]

It brings some comfort to know you found it weird too. 

In the end, we noted that the tunables were in ‘legacy’ mode - a hold over from prior experimentation, and a possible source of how we ended up with the remapped PGs in the first place.  Setting that back to ‘firefly’ cleared up the remaining two ‘remapped’ PGs, bringing them online and restoring the cluster to health.   

Thanks for the tips along the way to getting back to ‘healthy’ Greg!   (and it would still be great to have a targeted command to kick a PG) 

On May 7, 2015, at 8:58 PM, Gregory Farnum <greg@xxxxxxxxxxx> wrote:

This is pretty weird to me. Normally those PGs should be reported as
active, or stale, or something else in addition to remapped. Sam
suggests that they're probably stuck activating for some reason (which
is a state in new enough code, but not all versions), but I can't tell
or imagine why from these settings. You might have hit a bug I'm not
familiar with that will be jostled by just restarting the OSDs in
question... :/
-Greg

_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com