Bug #54524
openthe bucket resharding logs should be INFO and not ERROR?
0%
Description
2022-03-10T13:51:49.348+0000 7fe660162700 0 req 6745898533330192612 315.525390625s swift:put_obj block_while_resharding ERROR: bucket is still resharding, please retry 2022-03-10T12:00:02.906+0000 7fe711ac5700 0 rgw index completion thread: ERROR: process(): bucket index completion failed, obj=mycontainers1:myobjects48266839 r=-2300 2022-03-10T12:02:40.818+0000 7fe7122c6700 0 process_entry: Error during resharding bucket mycontainers1:(16) Device or resource busy
- We know these messages are just for information purposes that the bucket is busy with resharding showing them in ERROR creates confusion, we think they should be INFO?
Updated by Casey Bodley about 2 years ago
- Status changed from New to Triaged
- Assignee set to J. Eric Ivancich
Updated by J. Eric Ivancich about 2 years ago
- Status changed from Triaged to Need More Info
A failure to reshard seems like it deserves at least a WARNING (1st and 3rd examples).
Your 2nd example looks like a failure to complete a bucket index transaction. That seems like an error to me.
What do others think?
Updated by Vikhyat Umrao about 2 years ago
J. Eric Ivancich wrote:
Thanks, Eric.
A failure to reshard seems like it deserves at least a WARNING (1st and 3rd examples).
But I think again this is not a real failure it is just that some other RGW process is trying to reshard when the bucket is already been resharded from a different RGW? So maybe in warning with better explanation in the log message - may be changing a little bit log message?
Your 2nd example looks like a failure to complete a bucket index transaction. That seems like an error to me.
Please check the RHBZ comment - https://bugzilla.redhat.com/show_bug.cgi?id=2062855#c7 looks like this is again a non-fatal error.
What do others think?