So from what I am understanding is that there is no need to monitor this and no need to remember running repair? If that's the case then manual repair wouldn't be needed ever, correct?
But if Manual repair is needed then shouldn't there be ability to monitor? Having dealt with production problems I know how handy these monitoring can be. In our case there generally is development team and then operations team. Operations team is generally monitoring system and may not know about diff. scnearios like GCGracePeriod. I would say anything manual that someone need to be done there should be some ability to monitor that to have a successful operations. And nothing better if Cassandra can expose that ability. Otherwise we will need yet another way of reminding us to run repair :) -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/How-to-determine-if-repair-need-to-be-run-tp6220005p6221041.html Sent from the cassandra-u...@incubator.apache.org mailing list archive at Nabble.com.
