Project

General

Profile

Actions
Copy link

Bug #23548

closed

Discard ops should flush affected objects from in-memory cache

Added by Jason Dillaman about 6 years ago. Updated over 5 years ago.

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

0%

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

Description

When using the in-memory cache in writeback mode, it's possible that an overlapping discard immediately after a write will result in the writeback operation racing w/ the discard.

Related issues 2 (0 open — 2 closed)

Copied to rbd - Backport #23604: luminous: Discard ops should flush affected objects from in-memory cacheResolvedJason DillamanActions
Copied to rbd - Backport #23605: jewel: Discard ops should flush affected objects from in-memory cacheClosedActions
Actions
Copy link
 #1

Updated by Jason Dillaman about 6 years ago

  • Status changed from In Progress to Fix Under Review
Actions
Copy link
 #2

Updated by Mykola Golub about 6 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions
Copy link
 #3

Updated by Nathan Cutler about 6 years ago

  • Copied to Backport #23604: luminous: Discard ops should flush affected objects from in-memory cache added
Actions
Copy link
 #4

Updated by Nathan Cutler about 6 years ago

  • Copied to Backport #23605: jewel: Discard ops should flush affected objects from in-memory cache added
Actions
Copy link
 #7

Updated by Jason Dillaman over 5 years ago

  • Status changed from Pending Backport to Resolved
Actions
Copy link

Also available in: Atom PDF