[SRU] rgw: unable to abort multipart upload after the bucket got resharded
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Cloud Archive |
Fix Released
|
Undecided
|
Unassigned | ||
Queens |
Fix Released
|
High
|
Unassigned | ||
Rocky |
Won't Fix
|
Undecided
|
Unassigned | ||
Stein |
Fix Released
|
Undecided
|
Unassigned | ||
Train |
Fix Released
|
Undecided
|
Unassigned | ||
ceph (Ubuntu) |
Fix Released
|
Undecided
|
dongdong tao | ||
Bionic |
Fix Released
|
High
|
Unassigned |
Bug Description
[Impact]
This bug will cause the bucket not able to abort the multipart upload and leaving the stale multiple entries behind for those buckets which had partial multipart uploads before the resharding.
[Test Case]
Deploy a latest luminous(12.2.13) ceph cluter
Create a bucket
upload a big file (200M+) to that bucket
Press "Ctrl + C" after several part (each part is 15M) had been uploaded
Manually reshard the bucket to 4 shards
Abort the multipart uploading
Without the fix, you will not able to abort the previous uploading
[Regression Potential]
Low - this fix has been accept upstream in later releases since from Mimic, but it there is a super large multipart uploads, all the multi-entry will now be correctly mapped to the expected shard, which will cause this shard contain more omap entries than before, which might some slow when listing the shard
[Original Bug Report]
There is a bug during the resharding for those multipart entries.
For all the multipart entries, the hash source should be the object name so that all those entries can still be
distributed to one same bucket index shard object.
Right now the code just calculate the shard id based on each entry's name, which is wrong
This can cause the bucket not able to abort the multipart upload and leave the stale multiple entries behind.
https:/
Changed in ceph (Ubuntu): | |
assignee: | nobody → dongdong tao (taodd) |
tags: | added: sts sts-sru-needed |
tags: |
added: verification-bionic-done verification-done removed: verification-needed verification-needed-bionic |
tags: |
added: verification-queens-done removed: verification-queens-needed |
tags: |
added: verification-done removed: verification-needed |
tags: |
added: verification-done-bionic removed: verification-bionic-done |
I have specifically not raised a bug target for eoan as the fix for this issue is included in 14.2.8 which is the proposed UNAPPROVED queue for SRU team review.