> This isn’t really the whole story. The amount of wasted scans on index
repairs is negligible. If a difference is detected with snapshot repairs
though, you have to read the entire partition from both the view and base
table to calculate what needs to be fixed.
You nailed it.
When the base table
> We potentially have to do it several times on each node, depending on
the size of the range. Smaller ranges increase the size of the board
exponentially, larger ranges increase the number of SSTables that would be
involved in each compaction.
As described in the CEP example, this can be handled
You can detect and fix the mismatch in a single round of repair, but the amount
of work needed to do it is _significantly_ higher with snapshot repair.
Consider a case where we have a 300 node cluster w/ RF 3, where each view
partition contains entries mapping to every token range in the cluster
