We are running repair -pr. We've tried subrange manually and that seems to work ok. I guess we'll go with that going forward. Thanks for all the info!
On Mon, Jun 30, 2014 at 6:52 PM, Jaydeep Chovatia < chovatia.jayd...@gmail.com> wrote: > Are you running full repair or on subset? If you are running full repair > then try running on sub-set of ranges which means less data to worry during > repair and that would help JAVA heap in general. You will have to do > multiple iterations to complete entire range but at-least it will work. > > -jaydeep > > > On Mon, Jun 30, 2014 at 3:22 PM, Robert Coli <rc...@eventbrite.com> wrote: > >> On Mon, Jun 30, 2014 at 3:08 PM, Yuki Morishita <mor.y...@gmail.com> >> wrote: >> >>> Repair uses snapshot option by default since 2.0.2 (see NEWS.txt). >>> >> >> As a general meta comment, the process by which operationally important >> defaults change in Cassandra seems ad-hoc and sub-optimal. >> >> For to record, my view was that this change, which makes repair even >> slower than it previously was, was probably overly optimistic. >> >> It's also weird in that it changes default behavior which has been >> unchanged since the start of Cassandra time and is therefore probably >> automated against. Why was it so critically important to switch to snapshot >> repair that it needed to be shotgunned as a new default in 2.0.2? >> >> =Rob >> >> > >
