Project

General

Profile

Bug #7168

404 Errors When save immediately follows a delete

Added by Xiangyu Lv about 10 years ago. Updated about 10 years ago.

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

0%

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

Description

If the delete operation clashed with the save, and the save returned an 404. Is there an option to make save successful anyway even though there are ongoing deletes?

The radosgw log:
2013-11-28 02:12:41.368090 7f118a643700 2 req 11275333:0.000072::HEAD /Flickr7454m/11093685123::initializing
2013-11-28 02:12:41.497465 7f118a643700 2 req 11275333:0.129447:s3:HEAD /Flickr7454m/11093685123:get_obj:http status=200
2013-11-28 02:12:41.499747 7f1242d6a700 1 ====== starting new request req=0x9c6fa0 ===== The delete op started
2013-11-28 02:12:41.499824 7f1242d6a700 2 req 11275346:0.000078::POST /Flickr7454m/::initializing
2013-11-28 02:12:41.501611 7f1242d6a700 2 req 11275346:0.001865:s3:POST /Flickr7454m/:multi_object_delete:reading permissions
2013-11-28 02:12:41.503435 7f1242d6a700 2 req 11275346:0.003689:s3:POST /Flickr7454m/:multi_object_delete:executing
2013-11-28 02:12:41.504509 7f116ee17700 1 ====== starting new request req=0xa25b20 ===== The PUT op started
2013-11-28 02:12:41.504577 7f116ee17700 2 req 11275348:0.000069::PUT /Flickr7454m/11093685123::initializing
2013-11-28 02:12:41.509087 7f116ee17700 2 req 11275348:0.004578:s3:PUT /Flickr7454m/11093685123:put_obj:reading permissions
2013-11-28 02:12:41.651838 7f1242d6a700 1 ====== req done req=0x9c6fa0 http_status=200 ====== The delete op succeeded
2013-11-28 02:12:41.734639 7f116ee17700 2 req 11275348:0.230131:s3:PUT /Flickr7454m/11093685123:put_obj:http status=404
2013-11-28 02:12:41.734730 7f116ee17700 1 ====== req done req=0xa25b20 http_status=404 ====== The PUT op failed

Associated revisions

Revision 5c24a7ea (diff)
Added by Yehuda Sadeh about 10 years ago

rgw: don't return -ENOENT in put_obj_meta()

Fixes: #7168

An object put may race with the same object's delete. In this case just
ignore the error, same behavior as if object was created and then
removed.

Signed-off-by: Yehuda Sadeh <>

Revision 1e2984ac (diff)
Added by Yehuda Sadeh about 10 years ago

rgw: don't return -ENOENT in put_obj_meta()

Fixes: #7168

An object put may race with the same object's delete. In this case just
ignore the error, same behavior as if object was created and then
removed.

Signed-off-by: Yehuda Sadeh <>
(cherry picked from commit 5c24a7ea905587fd4077e3b0cfc0f5ad2b178c29)

History

#1 Updated by Yehuda Sadeh about 10 years ago

  • Status changed from New to 12
  • Priority changed from Normal to High

#2 Updated by Yehuda Sadeh about 10 years ago

  • Status changed from 12 to Fix Under Review

#3 Updated by Yehuda Sadeh about 10 years ago

  • Assignee set to Josh Durgin

#4 Updated by Yehuda Sadeh about 10 years ago

  • Backport set to dumpling

#5 Updated by Josh Durgin about 10 years ago

  • Status changed from Fix Under Review to Pending Backport
  • Assignee changed from Josh Durgin to Yehuda Sadeh

commit:86c15480fc3e33b9a3b84d0af68d8398fc732bae

#6 Updated by Yehuda Sadeh about 10 years ago

  • Status changed from Pending Backport to Resolved

Fix landed dumpling at commit:1e2984ac4a4ed0508e1b5efc8b69ae4da0cac824, and commit:ba792cdc8d0c006e260e6a02a33ca1491b35901c.

Also available in: Atom PDF