Project

General

Profile

Feature #9981

Updated by Sage Weil over 6 years ago

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.

Back