Eugen Block wrote: > The large omap objects are discovered during deep-scrub, so you just have to > deep-scrub the PG again to clear the warning.
That did it, thanks. I was quite close, though - I tried to scrub the PG instead of deep scrub :-) Thanks again! -Yenya > Zitat von Jan Kasprzak <[email protected]>: > > > Hello, Ceph users, > > > > on my Ceph cluster with my custom rgw-like front-end client storing > > metadata to omap I got "1 large omap objects" warning. According to cluster > > log, the large object is > > > > osd.39 (osd.39) 2292 : cluster [WRN] Large omap object found. Object: > > 76:0bfe63c7:::idx.00000000004:head PG: 76.e3c67fd0 (76.10) Key count: > > 259173 Size (bytes): 12440304 > > > > I have increased the limit using > > > > ceph config set osd osd_deep_scrub_large_omap_object_key_threshold 1000000 > > > > but the warning still remains. How can I get rid of the warning after > > increasing the size limit? > > > > Thanks! > > > > -Yenya > > > > -- > > | Jan "Yenya" Kasprzak <kas at {fi.muni.cz - work | yenya.net - private}> | > > | https://www.fi.muni.cz/~kas/ GPG: 4096R/A45477D5 | > > We all agree on the necessity of compromise. We just can't agree on > > when it's necessary to compromise. --Larry Wall > > _______________________________________________ > > ceph-users mailing list -- [email protected] > > To unsubscribe send an email to [email protected] > > > _______________________________________________ > ceph-users mailing list -- [email protected] > To unsubscribe send an email to [email protected] -- | Jan "Yenya" Kasprzak <kas at {fi.muni.cz - work | yenya.net - private}> | | https://www.fi.muni.cz/~kas/ GPG: 4096R/A45477D5 | We all agree on the necessity of compromise. We just can't agree on when it's necessary to compromise. --Larry Wall _______________________________________________ ceph-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
