Return-Path: 
 <user-return-19043-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org>
X-Original-To: apmail-cassandra-user-archive@www.apache.org
Delivered-To: apmail-cassandra-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id F0FDF74D4
	for <apmail-cassandra-user-archive@www.apache.org>;
 Fri, 22 Jul 2011 07:55:51 +0000 (UTC)
Received: (qmail 55194 invoked by uid 500); 22 Jul 2011 07:55:49 -0000
Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org
Received: (qmail 54500 invoked by uid 500); 22 Jul 2011 07:55:38 -0000
Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@cassandra.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@cassandra.apache.org>
List-Post: <mailto:user@cassandra.apache.org>
List-Id: <user.cassandra.apache.org>
Reply-To: user@cassandra.apache.org
Delivered-To: mailing list user@cassandra.apache.org
Received: (qmail 54430 invoked by uid 99); 22 Jul 2011 07:55:35 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Jul 2011 07:55:35 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of jonathan.colby@gmail.com
 designates 209.85.215.70 as permitted sender)
Received: from [209.85.215.70] (HELO mail-ew0-f70.google.com) (209.85.215.70)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Jul 2011 07:55:28 +0000
Received: by ewy9 with SMTP id 9so956205ewy.1
        for <user@cassandra.apache.org>; Fri, 22 Jul 2011 00:55:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.60.201 with SMTP id u51mr108682wec.4.1311321307156; Fri,
 22 Jul 2011 00:55:07 -0700 (PDT)
Message-ID: <000e0cd6e2f4b3142904a8a3c8a7@google.com>
Date: Fri, 22 Jul 2011 07:55:07 +0000
Subject: eliminate need to repair by using column TTL??
From: jonathan.colby@gmail.com
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=000e0cd6e2f4b3141704a8a3c8a4

--000e0cd6e2f4b3141704a8a3c8a4
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes

One of the main reasons for regularly running repair is to make sure  
deletes are propagated in the cluster, ie, data is not resurrected if a  
node never received the delete call.

And repair-on-read takes care of repairing inconsistencies "on-the-fly".

So if I were to set a universal TTL on all columns - so everything would  
only live for a certain age, would I be able to get away without having to  
do regular repairs with nodetool?

I realize this scenario would not be applicable for everyone, but our data  
model would allow us to do this.

So could this be an alternative to running the (resource-intensive,  
long-running) repairs with nodetool?

Thanks.

--000e0cd6e2f4b3141704a8a3c8a4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

One of the main reasons for regularly running repair is to make sure delete=
s are propagated in the cluster, i.e., data is not resurrected if a node ne=
ver received the delete call.<br /><br />And repair-on-read takes care of r=
epairing inconsistencies &quot;on-the-fly&quot;.<br /><br />So if I were to=
 set a universal TTL on all columns - so everything would only live for a c=
ertain age,   would I be able to get away without having to do regular repa=
irs with nodetool?<br /><br />I realize this scenario would not be applicab=
le for everyone, but our data model would allow us to do this. <br /><br />=
So could this be an alternative to running the (resource-intensive, long-ru=
nning) repairs with nodetool?<br /><br />Thanks.
--000e0cd6e2f4b3141704a8a3c8a4--