On 01/11/2011 10:11 AM, Edward Capriolo wrote: > I think because the RowCache is only saved periodically it could be > out of sync. IE saved at 12:00 changed at 12:01 then the row cache > would consistently return the wrong results since it never looks at > the disk again. I guess saving the row cache only makes sense for a > smaller row cache at this point.
This makes total sense and is obvious in hindsight. But wouldn't such a hypothetical "stale" row cache on be corrected by read repair (in other words useless for write heavy workloads, not a problem for read heavy)?
