Hello there,

We have a 3 node cluster with Cassandra 2.0.8 version. I am seeing data
that should be dropped already. In JMX, I can see that
DroppableTombstoneRatio is 0.68 for the column family and the
tombstone_threshold was left as default for the CF. We are using LCS on
related CF and replication factor of keyspace is set to 3.

We have experienced some downtimes because of "repair" and for that reason,
we are reluctant to run repair again.

How can we get rid of this tombstoned data without running repair? Or are
there any other way to run repair without exhausting the cluster? I have
seen a lot about "repair -pr", however I am not sure if it will be suitable
for our case.

Regards,
Safa T.

Reply via email to