A TTL is technically similar to a delete - in the end both create tombstones. If you want to eliminate the possibility of resurrected deleted data, you should run repairs.
If you can guarantuee a 100% that data is read-repaired before gc_grace_seconds after the data has been TTL'ed, you won't need an extra repair. 2017-02-27 18:29 GMT+01:00 Oskar Kjellin <oskar.kjel...@gmail.com>: > Are you running multi dc? > > Skickat från min iPad > > 27 feb. 2017 kl. 16:08 skrev Thakrar, Jayesh <jthak...@conversantmedia.com > >: > > Suppose I have an application, where there are no deletes, only 5-10% of > rows being occasionally updated (and that too only once) and a lot of reads. > > > > Furthermore, I have replication = 3 and both read and write are configured > for local_quorum. > > > > Occasionally, servers do go into maintenance. > > > > I understand when the maintenance is longer than the period for > hinted_handoffs to be preserved, they are lost and servers may have stale > data. > > But I do expect it to be rectified on reads. If the stale data is not read > again, I don’t care for it to be corrected as then the data will be > automatically purged because of TTL. > > > > In such a situation, do I need to have a periodic (weekly?) manual/batch > read_repair process? > > > > Thanks, > > Jayesh Thakrar > > -- Benjamin Roth Prokurist Jaumo GmbH · www.jaumo.com Wehrstraße 46 · 73035 Göppingen · Germany Phone +49 7161 304880-6 · Fax +49 7161 304880-1 AG Ulm · HRB 731058 · Managing Director: Jens Kammerer
