Ceph » rgw

Bug #16412

Updated by Michael Kidd almost 8 years ago

Observed behavior: 
 * In an environment with bucket index sharding enabled, deletion of a bucket leaves behind the bucket index shards. 

 Desired behavior: 
 * When a bucket is deleted, all bucket index shards should be deleted. 

 Reproduction: 
 * Enable bucket index sharding: 
   rgw_override_bucket_index_max_shards = 32 
 * Create buckets 
 * Delete buckets 
 * List contents of bucket index pool 

 Attempted deleting the bucket data with the following three methods, all with the exact same results: 
 <pre> 
 # 
  - s3cmd del --recursive s3://bucket-to-delete 
 # 
  - radosgw-admin bucket rm --bucket bucket-to-delete    --purge-objects 
 # 
  - radosgw-admin user rm --uid user-to-delete --purge-data 
 </pre> 

 Further, attempting to clean up with metadata rm does not help: 
 <pre> 
 # radosgw-admin metadata rm bucket:default.538200.103 
 </pre> 

 The deleted buckets do not show up with metadata list: 
 <pre> 
 # radosgw-admin metadata list --metadata-key="bucket.instance" | grep default.538200.103 -c 
 0 
 </pre> 

 But they do show up with rados ls: 
 <pre> 
 # rados ls -p .rgw.buckets.index | grep default.538200.103 -c 
 32 
 </pre> 

Back