Bug #34307
closedradosgw: dynamic resharding does not drop old bucket indexes
0%
Description
ceph mon now complains when omap numbers exceed a threshold (12.2.6+, master/mimic), which can easily happen with large bucket indexes. From luminous we have dynamic resharding which while shards the bucket indexes, still seems to keep the old bucket indexes around, which have the large index which pg deep scrub will report. Have a radosgw-admin option to list (and maybe clear) these buckets and indexes so that they may be easily removed by the administrator.
Updated by Abhishek Lekshmanan over 5 years ago
bash oneliner find these bucket indexes using rgw admin commands
$ radosgw-admin bucket stats > bucket-stat.out
$ grep -E '"bucket"|"id"|"marker"' bucket-stats.out | awk -F ":" '{print $2}' | while read -r bucket; do read -r id; read -r marker; [ "$id" == "$marker" ] && true || echo $bucket $id $marker
Updated by Matt Benjamin over 5 years ago
I thought that the design intent of resharding was that old indexes would be retired once resharding was successfully completed. It seems that behavior should at least be an option, and probably the default?
Matt
Updated by Vikhyat Umrao over 5 years ago
Orit had created this bug - http://tracker.ceph.com/issues/24082 I hope it is related to dynamic sharding.
Updated by Casey Bodley almost 5 years ago
- Status changed from New to Resolved
- Assignee deleted (
Orit Wasserman)