On Fri, Aug 16, 2013 at 5:47 AM, Mostowiec Dominik <Dominik.Mostowiec@xxxxxxxxxxxx> wrote: > Hi, > Thanks for your response. > >> It's possible, as deep scrub in particular will add a bit of load (it >> goes through and compares the object contents). > > It is possible that the scrubbing blocks access(RW or only W) to bucket index when check .dir... file? > When rgw index is very large I guess it take some time. Yes, it definitely can as scrubbing takes locks on the PG, which will prevent reads or writes while the message is being processed (which will involve the rgw index being scanned). >> Are you not having any >> flapping issues any more, and did you try and find when it started the >> scrub to see if it matched up with your troubles? > > No, I didn't. > But on our second cluster with the same problem, disable scrubbing also helps. > >> I'd be hesitant to turn it off as scrubbing can uncover corrupt >> objects etc, but you can configure it with the settings at >> http://ceph.com/docs/master/rados/configuration/osd-config-ref/#scrubbing. >> (Always check the surprisingly-helpful docs when you need to do some >> config or operations work!) > > I think change config scrub timeout or interval don't full remove issues. > Change "osd deep scrub stride" to small value make scrubbing lightest? You probably don't want to change the scrub stride; that is used to keep reads at an appropriate size for the internal control threads but won't relate to the object read/write locking. -Greg Software Engineer #42 @ http://inktank.com | http://ceph.com _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com