Current master works ok with error objects in log. However, it seems that old ones print the table pointer instead of error object, e.g.
2026-05-23 18:50:53.396 [402275] main/128/vshard.recovery log_ratelimit.lua:136 E> Error during searching in cluster for recovery of 9 bucket: table: 0x402b2f78
It can be fixed by logging as follows:
limiter:log_error(err, 'Error during searching in cluster for recovery of ' ..
'%d bucket: %s', bucket_id, json_encode(err))Related #624
Current master works ok with error objects in
log. However, it seems that old ones print the table pointer instead of error object, e.g.It can be fixed by logging as follows:
Related #624