On 6/12/20, 5:40 AM, "James, GleSYS" <james.mcewan(a)glesys.se> wrote:
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 can – somewhat happily – confirm that setting debug_rgw to "20/1" makes the
issue disappear instantly. Even if the RGW is in the middle of a "stuck"
listing, the debug level change causes the load to drop and results appear on the client
almost instantly. After setting debug_rgw back to "5/1" the listings get stuck
again, which in our case is not just occasionally, but always and for every bucket. Not
exactly a solution, since we're already having some trouble keeping the docker
container logs to a manageable size, but might be good enough as a workaround.
Not sure how we can find out steps to reproduce the issue in the first place. Happy to do
some testing if anyone has suggestions. Also, I'm inclined to report this as a bug at
this point unless there's opposing advice.
Thanks,
Stefan