Den ons 20 maj 2020 kl 05:23 skrev Szabo, Istvan (Agoda) <
Istvan.Szabo@xxxxxxxxx>:
> LARGE_OMAP_OBJECTS 1 large omap objects
> 1 large objects found in pool 'default.rgw.log'
> When I look for this large omap object, this is the one:
> for i in `ceph pg ls-by-pool default.rgw.log | tail -n +2 | awk '{print
> $1}'`; do echo -n "$i: "; ceph pg $i query |grep num_large_omap_objects |
> head -1 | awk '{print $2}'; done | grep ": 1"
> 4.d: 1
> I found only this way to reduce the size:
> radosgw-admin usage trim --end-date=2019-05-01 --yes-i-really-mean-it
>
> However when this is running the RGW became completely unreachable, the
> loadbalancer started to flapping and users started to complain because they
> can't do anything.
> Is there any other way to fix it, or any suggestion why this issue happens?
>
If you are not using the usage logs for anything, there are options in rgw
to not produce them, which is a blunt but working solution to not have to
clean them out with outages during trimming.
If you do use them, perhaps set "rgw usage max user shards" to something
larger than the default 1.
--
May the most significant bit of your life be positive.
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
