Project

General

Profile

Actions

Bug #21596

closed

failed CompleteMultipartUpload request does not release lock

Added by Casey Bodley over 6 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Target version:
-
% Done:

0%

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

Description

A rados lock is used to prevent racing CompleteMultipartUpload requests on the same object. But if we fail the request (due to invalid arguments, missing parts, etc), the lock is not released.

So after a failed CompleteMultipartUpload request, all later CompleteMultipartUpload requests on that object will fail with '500 Internal Error' for a duration of rgw_mp_lock_max_time (default: 10 minutes). The radosgw log prints:

RGWCompleteMultipart::execute() failed to acquire lock


Related issues 2 (0 open2 closed)

Copied to rgw - Backport #21695: luminous: failed CompleteMultipartUpload request does not release lockResolvedAbhishek LekshmananActions
Copied to rgw - Backport #21873: jewel: failed CompleteMultipartUpload request does not release lockResolvedMatt BenjaminActions
Actions

Also available in: Atom PDF