The method I've used in the past to initiate a repair quickly was to set osd_max_deep_scrubs to 0 across the cluster and then set it to 2 on only the osds that were involved in the pg. Alternatively you could just increase that setting to 3 or more on only those osds involved in the pg to trigger the pg to start repairing, but that will allow those osds to potentially have multiple deep scrubs happening at the same time.
On Fri, Dec 15, 2017 at 9:03 AM Vincent Godin <vince.mlist@xxxxxxxxx> wrote:
We have some scrub errors on our cluster. A ceph pg repair x.xxx is
take in account only after hours. It seems to be linked to deep-scrubs
which are running at the same time. It 's look like it has to wait for
a slot before launching the repair. I have then two question :
is it possible to launch a repair while the flag nodeep-scrub is set ?
is it possible to raise priority of the pg repair for it to start quickly ?
Thanks
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
