Project

General

Profile

Actions

Bug #56510

closed

bucket index objects still exist after bucket deletion

Added by Chris Durham almost 2 years ago. Updated over 1 year ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Target version:
% Done:

0%

Source:
Community (user)
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

I am using ceph 16.2.7 on Rocky Linux 8.5

Bucket index objects, such as .dir.<zoneid>.<bucketid>.N, where there are N objects based on the number of index shards the bucket had, still exist after an s3 bucket deletion. These are in the the index pool, of course. They still exist after a radosgw-admin gc process --include-all,
but I am not sure if that matters.

This is a multisite with two zones (1 at each site) that replicate in both directions. The index objects persist on both sides' index pool.

These clusters originally started at 15.2.x and have been upgraded. The bucket used for this test was created after the upgrade. But a similar bucket that was
created before the upgrade and was deleted before the upgrade still has its index objects in the index pool.

I see a really old ticket, https://tracker.ceph.com/issues/16412 that at least suggests it was 'fixed' in the past.

Please advise


Related issues 1 (1 open0 closed)

Is duplicate of rgw - Bug #20802: rgw multisite: clean up deleted bucket instance and index objectsFix Under ReviewShilpa MJ

Actions
Actions #1

Updated by Casey Bodley almost 2 years ago

  • Is duplicate of Bug #20802: rgw multisite: clean up deleted bucket instance and index objects added
Actions #2

Updated by Casey Bodley almost 2 years ago

  • Status changed from New to Duplicate
Actions #3

Updated by Ilya Dryomov over 1 year ago

  • Target version changed from v16.2.10 to v16.2.11
Actions

Also available in: Atom PDF