Ceph » rgw

I have 2 more observations to add here.

1. when I restarted the gateways, the dynamic resahrding kicked in as expected at least on the primary site. On the secondary, we see the error https://tracker.ceph.com/issues/52877 after restarting gateways.

2. radosgw-admin reshard list does not show any entry.

3. 'RGWReshard::process_entry > I do not see these error messages in the rgw logs. What would be the debugging level for this to get populated in the logs?

Vidushi Mishra wrote:

I have 2 more observations to add here.

1. when I restarted the gateways, the dynamic resahrding kicked in as expected at least on the primary site. On the secondary, we see the error https://tracker.ceph.com/issues/52877 after restarting gateways.

huh, i don't see why restart would be required

those "failed to list reshard log entries" error messages on the secondary are just noise, and wouldn't prevent any pending reshards

2. radosgw-admin reshard list does not show any entry.

can you clarify this one? if 'reshard list' is empty, i assume that would mean everything resharded successfully on that zone

3. 'RGWReshard::process_entry > I do not see these error messages in the rgw logs. What would be the debugging level for this to get populated in the logs?

errors there would be at log level 0, so they'd show up without special configuration

but it's worth running the gateways under --debug-rgw=20 to make sure we see messages like these every ~10 minutes:

rgw reshard worker thread: processing logshard = x
rgw reshard worker thread: finish processing logshard = x