Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAPVoXPz1sLYht2ZZXR1q5cSLSj40pShPm7PkBSDeL+zUtqCJWw@mail.gmail.com>
References: 
 <CAPVoXPz1sLYht2ZZXR1q5cSLSj40pShPm7PkBSDeL+zUtqCJWw@mail.gmail.com>
Date: Wed, 22 Aug 2012 11:59:15 -0700
Message-ID: 
 <CACHzRHbtHaFTb_9AX3q9mOq8OFm-FkahA-3FmTnW=1Mb8oQC_Q@mail.gmail.com>
Subject: Re: nodetool repair - when is it not needed ?
From: Rob Coli <rcoli@palominodb.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Aug 22, 2012 at 8:37 AM, Senthilvel Rangaswamy
<senthilvel@gmail.com> wrote:
> We are running Cassandra 1.1.2 on EC2. Our database is primarily all
> counters and we don't do any
> deletes.
>
> Does nodetool repair do anything for such a database. All the docs I read
> for nodetool repair suggests
> that nodetool repair is needed only if there is deletes.

Since 1.0, repair is only needed if a node crashes. If a node crashes,
my understanding is that a cluster-wide repair (with -pr on each node)
is required, because the crashed node could have lost a hint for any
other node.

https://issues.apache.org/jira/browse/CASSANDRA-2034

=Rob

-- 
=Robert Coli
AIM&GTALK - rcoli@palominodb.com
YAHOO - rcoli.palominob
SKYPE - rcoli_palominodb