For the cases where repair brings down a cluster, I can safely say that cluster has more problems than just repair. Consider the load caused by repair to be somewhat equivalent to losing a node. This is not a 1 for 1 comparison, as the node you're running repair on is up albeit busy,and the potential streaming impacts can be of course worse, however, the entire design of Cassandra is around being able to tolerate 1 or more node outages (depending on your level of sizing) and not have your application be affected.
On Thu, Jan 22, 2015 at 1:15 PM, SEGALIS Morgan <msega...@gmail.com> wrote: > Don't think it is near failure, it uses only 3% of the CPU and 40% of the > RAM if that is what you meant. > > 2015-01-22 19:58 GMT+01:00 Robert Coli <rc...@eventbrite.com>: > >> On Thu, Jan 22, 2015 at 10:53 AM, SEGALIS Morgan <msega...@gmail.com> >> wrote: >> >>> what do you mean by "operating correctly" ? >>> >> >> I mean that if you are operating near failure, repair might trip a node >> into failure. But if you are operating correctly, repair should not. >> >> =Rob >> >> > > > > -- > Morgan SEGALIS > -- Thanks, Ryan Svihla
