Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of watanabe.maki@gmail.com
 designates 74.125.83.172 as permitted sender)
References: <BANLkTik4HynV=GnzMi3n8OAa20HFSzej5g@mail.gmail.com>
 <BANLkTindb2CrWaQeRp9NFGnu9FZk2-svug@mail.gmail.com>
 <BANLkTik98gYBMeBxBUVovA91LGq+fJQtLA@mail.gmail.com>
 <BANLkTi==7NzEDOxXJHNfpMJLBXzeJNq1uQ@mail.gmail.com>
In-Reply-To: <BANLkTi==7NzEDOxXJHNfpMJLBXzeJNq1uQ@mail.gmail.com>
Mime-Version: 1.0 (iPhone Mail 8G4)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii
Message-Id: <189C3828-FA2D-4F0E-902A-3E84FC1E110D@gmail.com>
Cc: "user@cassandra.apache.org" <user@cassandra.apache.org>
From: Watanabe Maki <watanabe.maki@gmail.com>
Subject: Re: Meaning of 'nodetool repair has to run within GCGraceSeconds'
Date: Fri, 1 Jul 2011 09:51:41 +0900
To: "user@cassandra.apache.org" <user@cassandra.apache.org>

Repair doesn't compact. Those are different processes already.

maki


On 2011/07/01, at 7:21, A J <s5alye@gmail.com> wrote:

> Thanks all !
> In other words, I think it is safe to say that a node as a whole can
> be made consistent only on 'nodetool repair'.
>=20
> Has there been enough interest in providing anti-entropy without
> compaction as a separate operation (nodetool repair does both) ?
>=20
>=20
> On Thu, Jun 30, 2011 at 5:27 PM, Jonathan Ellis <jbellis@gmail.com> wrote:=

>> On Thu, Jun 30, 2011 at 3:47 PM, Edward Capriolo <edlinuxguru@gmail.com> w=
rote:
>>> Read repair does NOT repair tombstones.
>>=20
>> It does, but you can't rely on RR to repair _all_ tombstones, because
>> RR only happens if the row in question is requested by a client.
>>=20
>> --
>> Jonathan Ellis
>> Project Chair, Apache Cassandra
>> co-founder of DataStax, the source for professional Cassandra support
>> http://www.datastax.com
>>=20