good points Aaron. I realize now how expensive repair on reads are. I'm
going to keep doing repairs regularly but still have a max TTL on all
columns to make sure we don't have really old data we no longer need
getting buried in the cluster.
On , aaron morton wrote:
Read repair will only r
Read repair will only repair data that is read on the nodes that are up at that
time, and does not guarantee that any changes it detects will be written back
to the nodes. The diff mutations are async fire and forget messages which may
go missing or be dropped or ignored by the recipient just li
One of the main reasons for regularly running repair is to make sure
deletes are propagated in the cluster, ie, data is not resurrected if a
node never received the delete call.
And repair-on-read takes care of repairing inconsistencies "on-the-fly".
So if I were to set a universal TTL on al
