Project

General

Profile

Actions

Bug #69013

closed

crimson: invalidate obc on replica even if referenced

Added by Samuel Just over 1 year ago. Updated 11 months ago.

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

0%

Source:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Tags (freeform):
Merge Commit:
Fixed In:
Released In:
Upkeep Timestamp:

Description

It's actually possible for an obc to be referenced by a replica read concurrently with the replica processing a repop on that object. Our existing tests don't really trigger that case because it would require the client to send a read racing with the write and the result of such a read would be timing dependent as to whether it sees the object version before or after currently outstanding writes.

Actions #1

Updated by Samuel Just over 1 year ago

  • Status changed from New to In Progress
Actions #2

Updated by Samuel Just 11 months ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF