|
Hi,
When i start a deep scrub on a PG by hand 'ceph pg deep-scrub 1.18d5', sometimes the deep scrub is executed direct after the command is entered, but often it's not there is a lot of time between starting and executing. For example: 2017-01-17 05:25:31.786 session 01162017 :: Starting deep-scrub on pg 1.1a39 for pool openstack_volumes2017-01-17 06:37:48.135325 osd.1120 <ip>:6814/4237 263 : cluster [INF] 1.1a39 deep-scrub starts 2017-01-17
06:58:07.651926 osd.1120 <ip>:6814/4237 264 : cluster [INF]
1.1a39 deep-scrub ok
De first log line is from our 'deep scrub cron script'. My question is, what defines how and when and how long a deep scrub is queued and is there a way to enforce the deep scrub 'now'. I am looking into this, because in the past we could deep scrub a specific set in 24 hours and now that's not possible anymore.
-- Regards, Richard. |
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
