Incremental repairs should also update the percentage, although I'd recommend not using incremental repair before 4.0. Just want to point out that running repairs based on repaired % isn't necessarily a bad thing, but it should be a secondary consideration. The important thing is to repair data more frequently than your gc grace period.
On October 4, 2017 at 1:33:57 PM, Javier Canillas (javier.canil...@gmail.com) wrote: That percentage will only be updated if you do a full repair. If you do repairs on local dc or with -pr, that percentage will not be updated. I scripted a regular repair on each node based on if this percentage is below some threshold. It has been running fine since several months ago. 2017-10-04 12:46 GMT-03:00 Blake Eggleston <beggles...@apple.com>: Not really no. There's a repaired % in nodetool tablestats if you're using incremental repair (and you probably shouldn't be before 4.0 comes out), but I wouldn't make any decisions based off it's value. On October 4, 2017 at 8:05:44 AM, ZAIDI, ASAD A (az1...@att.com) wrote: Hello folk, I’m wondering if there is way to find out list of table(s) which need repair OR if there Is way to find out what %age of data would need to be repaired on a table? Is such information available from Cassandra db engine through some other means? TIA~ Asad
