Bug #42531
when user stop multipart in the middle of uploading the parts that were in the middle of upload will stay on the data pool after abort the mp
0%
Description
when user stop multipart in the middle of uploading the parts that were in the middle of upload will stay on the data pool after abort the multipart.
Way to reproduce:
dd if=/dev/zero of=/tmp/zeros bs=1G count=1
s3cmd put /tmp/zeros s3://hello
Ctrl+C in the middle of the upload
s3cmd multipart s3://hello
s3cmd abortmp s3://hello/zeros <multipart_id>
radosgw-admin gc process --include-all
rados ls -p <rgw_data pool>
some objects of that multipart will be there
Related issues
History
#1 Updated by Casey Bodley almost 3 years ago
- Status changed from New to Triaged
I don't think this issue is specific to multipart uploads. I imagine you'd see the same behavior when writing a single large object.
#2 Updated by Casey Bodley over 2 years ago
- Assignee set to Or Friedmann
#3 Updated by Nathan Cutler over 2 years ago
- Status changed from Triaged to Pending Backport
- Backport set to nautilus
#4 Updated by Nathan Cutler over 2 years ago
- Copied to Backport #43942: nautilus: when user stop multipart in the middle of uploading the parts that were in the middle of upload will stay on the data pool after abort the mp added
#5 Updated by Nathan Cutler over 2 years ago
- Pull request ID set to 33017
#6 Updated by Nathan Cutler over 2 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".