Hi, I’m experiencing the same symptoms as OP.
We’re running Ceph Octopus 15.2.1 with RGW, and have seen on multiple occasions the bucket index pool go up to 500MB/s read throughput / 100K read IOPS. Our logs during this time are flooded with these entries: 2020-06-09T07:11:18.070+0200 7f2676efd700 1 RGWRados::Bucket::List::list_objects_ordered INFO ordered bucket listing requires read #1 When I set the debug_rgw logs to "20/1", the issue disappears immediately, and the throughput for the index pool goes back down to normal levels. I’ve not actually tried reproducing the issue myself as I assumed the problem was with the S3 client, but maybe this is a bug on the RGW side… Our bucket index pool is running on the same HDDs as the data pool, no separate SSDs like OP. Regards, James > On 12 Jun 2020, at 02:22, sw...@tiltworks.com wrote: > > Not seeing anything in OSD logs after triggering a listing, just heartbeat > entries. > _______________________________________________ > ceph-users mailing list -- ceph-users@ceph.io > To unsubscribe send an email to ceph-users-le...@ceph.io _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-le...@ceph.io
