Project

General

Profile

Bug #48268

rgw: when removing a current versioned object, the new current object doesn't get a new epoch

Added by Yehuda Sadeh over 3 years ago. Updated over 3 years ago.

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

0%

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

Description

E.g., we have an object with two versions, older one has epoch=2, new one has epoch=3. When removing the epoch=3 object, we're left with olh that has epoch=4, but the new current object has epoch=2. This can cause issues with multi-site such as having an object with no current version. Solution would be to either update the current obj with the new epoch, or to track epoch differently.

History

#1 Updated by Yehuda Sadeh over 3 years ago

  • Assignee set to Yehuda Sadeh

Also available in: Atom PDF