Project

General

Profile

Actions
Copy link

Bug #2120

closed

rgw: atomic write guard doesn't scale well

Added by Yehuda Sadeh about 12 years ago. Updated over 6 years ago.

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

0%

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

Description

shen there is a large number of writers to the same object.

Related issues 1 (0 open — 1 closed)

Related to Ceph - Feature #1956: rgw: revisit atomic GET/PUTResolved01/20/2012

Actions
Actions
Copy link
 #1

Updated by Greg Farnum about 12 years ago

Do we care? You can't do partial updates to objects IIRC, so many writers pretty much has to be wrong somehow or other.

Actions
Copy link
 #2

Updated by Yehuda Sadeh about 12 years ago

  • Source changed from Development to Community (user)

This was reported by a user through the ml. We should figure out with that user whether it's a real issue, or a red herring.

Actions
Copy link
 #3

Updated by Yehuda Sadeh about 12 years ago

Implementing #1956 would solve this issue, and would make the entire atomic scheme simpler.

Actions
Copy link
 #4

Updated by Sage Weil about 12 years ago

  • Target version set to v0.44
Actions
Copy link
 #5

Updated by Yehuda Sadeh about 12 years ago

A fix for that was already pushed (backing off when identifying a race in atomic write scheme). However, a more complete solution in which we provide a different atomic access scheme (#1956, #1847) is imminent.

Actions
Copy link
 #6

Updated by Yehuda Sadeh about 12 years ago

  • Status changed from New to Resolved
Actions
Copy link
 #7

Updated by John Spray over 6 years ago

  • Project changed from Ceph to rgw
  • Category deleted (22)
  • Target version deleted (v0.44)

Bulk reassign of radosgw category to RGW project.

Actions
Copy link

Also available in: Atom PDF