cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Tarbox <>
Subject Re: nodetool repair saying "starting" and then nothing, and nothing in any of the server logs either
Date Tue, 01 Jul 2014 19:05:50 GMT
"For what purpose are you running repair?"   Because I read that we should!

We do delete data from one column family quite regularly...from the other
CFs occasionally.  We almost never run with less than 100% of our nodes up.

In this configuration do we *need* to run repair?


On Tue, Jul 1, 2014 at 2:57 PM, Robert Coli <> wrote:

> On Tue, Jul 1, 2014 at 11:54 AM, Brian Tarbox <>
> wrote:
>> Given that an upgrade is (for various internal reasons) not an option at
>> this there anything I can do to get repair working again?  I'll
>> also mention that I see this behavior from all nodes.
> I think maybe increasing your phi tolerance for streaming timeouts might
> help.
> But basically, no. Repair has historically been quite broken in AWS. It
> was re-written in 2.0 along with the rest of streaming, and hopefully will
> soon stabilize and actually work.
> For what purpose are you running repair?
> =Rob

View raw message