Actions
Bug #46849
closedRGWObjVersionTracker does not track version over increments
% Done:
0%
Source:
Tags:
cache
Backport:
nautilus octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Description
after being used for a read-modify-write, RGWObjVersionTracker::apply_changes() will clear the read_version. this means later writes with that RGWObjVersionTracker will not call cls_version_check(), so lose the ability to detect racing writes. this read_version=0 will also get stored in the system object cache, so later read-modify-writes are also affected
Updated by Casey Bodley over 3 years ago
- Status changed from New to Fix Under Review
Updated by J. Eric Ivancich over 3 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler over 3 years ago
- Copied to Backport #47319: octopus: RGWObjVersionTracker does not track version over increments added
Updated by Nathan Cutler over 3 years ago
- Copied to Backport #47320: nautilus: RGWObjVersionTracker does not track version over increments added
Updated by Nathan Cutler over 3 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions