Project

General

Profile

Actions

Bug #23838

closed

save_torrent_file writes to omap (not atomic, not supported on ec pools)

Added by Casey Bodley almost 6 years ago. Updated about 1 year ago.

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

0%

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

Description

seed::save_torrent_file() stores torrent data in omap on the head object, which is not atomic with respect to other operations on the head object. and head objects are stored in the data pool, which is allowed be erasure-coded. in that case, attempts to use omap will fail

this torrent data should be stored in xattrs along with other attributes, so it can be written to the head object in the same transaction. moving it to attrs will require some backward-compatibility in get_torrent_file() to read from omap if we don't see the attribute


Related issues 1 (0 open1 closed)

Related to rgw - Bug #23506: [rgw] GET <object>?torrent returns object's body instead torrent-fileResolvedCasey Bodley03/29/2018

Actions
Actions #1

Updated by Casey Bodley almost 6 years ago

  • Related to Bug #23506: [rgw] GET <object>?torrent returns object's body instead torrent-file added
Actions #2

Updated by Casey Bodley about 1 year ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 50168
Actions #3

Updated by Casey Bodley about 1 year ago

  • Status changed from Fix Under Review to Resolved
Actions

Also available in: Atom PDF