Project

General

Profile

Actions

Feature #9981

closed

osd: cache: proxy writes (instead of unconditionally promoting)

Added by Sage Weil over 9 years ago. Updated over 8 years ago.

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

0%

Source:
other
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

This should work similar to the read recency checks that don't always promote on first read, but give the cache osd a choice.

Initially, use a similar (same?) tunable as the reads.

In the future, we can implement other heurstics, like not promoting on write_full (or very large writes), or deciding based on the IO hints in the client request.

Actions #1

Updated by Sage Weil over 9 years ago

  • Description updated (diff)
Actions #2

Updated by Sage Weil over 9 years ago

  • Target version deleted (0.90)
Actions #3

Updated by Greg Farnum over 9 years ago

One thing we'll need to be careful about when not promoting is how we handle snapshots. I don't remember exactly how that cooperation works, but I think it won't happen automatically if we aren't fetching the appropriate snaps history from the backend.

Actions #4

Updated by Sage Weil almost 9 years ago

  • Target version set to v9.0.4
Actions #5

Updated by Sage Weil almost 9 years ago

  • Status changed from New to In Progress
Actions #6

Updated by Samuel Just almost 9 years ago

  • Target version changed from v9.0.4 to v9.0.6
Actions #7

Updated by Samuel Just almost 9 years ago

  • Target version changed from v9.0.6 to v9.0.7
Actions #8

Updated by Sage Weil over 8 years ago

  • Target version changed from v9.0.7 to v9.0.8
Actions #9

Updated by Sage Weil over 8 years ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF