cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jaydeep Chovatia <>
Subject Re: nodetool repair -snapshot option?
Date Mon, 30 Jun 2014 22:52:43 GMT
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.


On Mon, Jun 30, 2014 at 3:22 PM, Robert Coli <> wrote:

> On Mon, Jun 30, 2014 at 3:08 PM, Yuki Morishita <>
> 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

View raw message