Instead of doing nodetool repair, is it not a cheaper operation to keep tab of failed writes (be it deletes or inserts or updates) and read these failed writes at a set frequency in some batch job ? By reading them, RR would get triggered and they would get to a consistent state.
Because these would targeted reads (only for those that failed during writes), it should be a shorter list and quick to repair (than nodetool repair). On Thu, Jun 30, 2011 at 5:27 PM, Jonathan Ellis <jbel...@gmail.com> wrote: > On Thu, Jun 30, 2011 at 3:47 PM, Edward Capriolo <edlinuxg...@gmail.com> > wrote: >> Read repair does NOT repair tombstones. > > It does, but you can't rely on RR to repair _all_ tombstones, because > RR only happens if the row in question is requested by a client. > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of DataStax, the source for professional Cassandra support > http://www.datastax.com >
