4 Mar
2021
4 Mar
'21
6:39 p.m.
вт, 2 мар. 2021 г. в 13:52, James Page <james.page@canonical.com>: (Disclaimer: I have never tried to run Ceph on bcache in production, and the test cluster was destroyed before reaching its first deep scrub)
b) turn off the sequential cutoff
sequential_cutoff = 0
This means that sequential writes will also always go to the cache device rather than the backing device
Could you please explain the exact mechanics of the sequential cutoff? Does it only affect big sequential writes, or big sequential reads too? I am asking because of the potential of deep scrubs being cached instead of the "real" hot data. -- Alexander E. Patrakov CV: http://u.pc.cd/wT8otalK