Hi If this problem was because of data inconsistencies, it should have been very rare. However, I am seeing this happen very often (almost 50 % of the times). Statistically, this should be very unlikely if the number of replication failures are small.
On Thu, Jun 25, 2015 at 11:55 PM, Tyler Hobbs <ty...@datastax.com> wrote: > > On Thu, Jun 25, 2015 at 1:00 PM, Robert Coli <rc...@eventbrite.com> wrote: > >> [1] or read repair set to 100% combined with a full scan of all data... >> which no one does... > > > And this is only true if "full scan" means reading every partition > individually. Reads of partition ranges (or a range slice, in old Thrift > terms) don't do read repair. > > > -- > Tyler Hobbs > DataStax <http://datastax.com/> > -- Aditya Shetty *Lead Engineer* *M*: +91 7022423545, *T*: 080 46603000 *EXT*: 4417 2nd FLOOR, WEST WING, SALARPURIA SUPREME, MARATHAHALLI, BENGALURU Download Our App [image: A] <https://play.google.com/store/apps/details?id=com.snapdeal.main&utm_source=mobileAppLp&utm_campaign=android> [image: A] <https://itunes.apple.com/in/app/snapdeal-mobile-shopping/id721124909?ls=1&mt=8&utm_source=mobileAppLp&utm_campaign=ios> [image: W] <http://www.windowsphone.com/en-in/store/app/snapdeal/ee17fccf-40d0-4a59-80a3-04da47a5553f>
