Bug 1475859 - [RFE] Add parallelism in radosgw-admin bucket rm command for bucket removal including S3/Swift API bucket rm calls
Summary: [RFE] Add parallelism in radosgw-admin bucket rm command for bucket removal ...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW
Version: 2.3
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: rc
: 5.0
Assignee: Matt Benjamin (redhat)
QA Contact: Tejas
URL:
Whiteboard:
: 1667236 (view as bug list)
Depends On:
Blocks: 1727980
TreeView+ depends on / blocked
 
Reported: 2017-07-27 13:33 UTC by Vikhyat Umrao
Modified: 2024-03-25 15:00 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-01 15:29:09 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-7623 0 None None None 2023-10-06 17:40:19 UTC

Description Vikhyat Umrao 2017-07-27 13:33:03 UTC
Description of problem:
[RFE] Add parallelism  in radosgw-admin bucket rm command for bucket removal

Customers/users are still reporting that bucket removal is slow with --bypass-gc and --inconsistent-index flags used:

radosgw-admin bucket rm --purge-objects --bypass-gc --inconsistent-index --bucket=<bucket name>


Version-Release number of selected component (if applicable):
Red Hat Ceph Storage 2.y

Comment 1 Vikhyat Umrao 2017-07-27 13:37:26 UTC
If we use --inconsistent-index and close the interrupt this command because of performance issue or some other reason we will have corrupted index and next time it will not allow deleting the bucket due to corrupted index then we need to run radosgw-admin bucket check --fix.

Comment 8 Vikhyat Umrao 2019-01-25 20:02:09 UTC
*** Bug 1667236 has been marked as a duplicate of this bug. ***

Comment 11 Giridhar Ramaraju 2019-08-05 13:06:01 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 12 Giridhar Ramaraju 2019-08-05 13:08:44 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri


Note You need to log in before you can comment on or make changes to this bug.