Bug #48329
opencls_rgw_gc_queue_remove_entries() doesn't remove entries from xattr urgent data
0%
Description
cls_rgw_gc_queue_remove_entries() has to scan the entries it's removing from the queue in order to also remove any urgent data entries that match removed queue entries. at the end of cls_rgw_gc_queue_remove_entries(), we re-encode the urgent data and write it back with queue_write_head()
however, once urgent data spills over to xattrs, each removed entry calls cls_cxx_getxattr("cls_queue_urgent_data") to check for a match in xattr_urgent_data_map. matching entries are removed from xattr_urgent_data_map, but the map never gets written back to the "cls_queue_urgent_data" xattr
p.s. similar to https://tracker.ceph.com/issues/48328, cls_rgw_gc_queue_remove_entries() should call cls_cxx_getxattr("cls_queue_urgent_data") once at the beginning instead of every entry
Updated by J. Eric Ivancich over 3 years ago
- Related to Bug #48330: rgw: fix GC defer process and clean up from immediate fix added
Updated by J. Eric Ivancich over 3 years ago
- Related to Bug #48328: inefficient check for xattr urgent data in cls_rgw_gc_queue_list_entries() added