From user-return-30037-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Sun Nov 11 09:52:03 2012 Return-Path: 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 87DA3DD2C for ; Sun, 11 Nov 2012 09:52:03 +0000 (UTC) Received: (qmail 463 invoked by uid 500); 11 Nov 2012 09:52:00 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 269 invoked by uid 500); 11 Nov 2012 09:51:59 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 231 invoked by uid 99); 11 Nov 2012 09:51:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 11 Nov 2012 09:51:58 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of andre.cruz@co.sapo.pt designates 212.55.140.20 as permitted sender) Received: from [212.55.140.20] (HELO sl.pt) (212.55.140.20) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 11 Nov 2012 09:51:50 +0000 Received: (qmail 14313 invoked from network); 11 Nov 2012 09:51:29 -0000 X-AntiVirus: PTMail-AV 0.3-0.95.1 X-Scan-Status: AV clean (0.05491 seconds); Received: from unknown (HELO [192.168.1.65]) (andre.cruz@sl.pt@[85.240.234.80]) (envelope-sender ) by mail-sl-pt02 (qmail-ldap-1.03) with AES128-SHA encrypted SMTP for ; 11 Nov 2012 09:51:29 -0000 From: =?iso-8859-1?Q?Andr=E9_Cruz?= Content-Type: multipart/alternative; boundary="Apple-Mail=_66114344-FEF7-4B2A-BDC0-61366CC914CC" Message-Id: Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: Strange delay in query Date: Sun, 11 Nov 2012 09:51:31 +0000 References: <274B0A13-59D2-4220-8711-36F370721DE4@co.sapo.pt> <4C258FB6-F8BF-43E2-B678-7BF8CECB2A49@co.sapo.pt> <305C0FD2-54AD-4AB9-B96C-F1D7539F744E@co.sapo.pt> To: In-Reply-To: X-Mailer: Apple Mail (2.1499) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_66114344-FEF7-4B2A-BDC0-61366CC914CC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Nov 11, 2012, at 12:01 AM, Binh Nguyen wrote: > FYI: Repair does not remove tombstones. To remove tombstones you need = to run compaction. > If you have a lot of data then make sure you run compaction on all = nodes before running repair. We had a big trouble with our system = regarding tombstone and it took us long time to figure out the reason. = It turned out that repair process also transfers TTLed data (compaction = is not triggered yet) to the other nodes even that data was removed from = the other nodes in the compaction phase before that. >=20 Aren't compactions triggered automatically? At least minor compactions. = Also, I read this in = http://www.datastax.com/docs/1.1/operations/tuning#tuning-compaction : "=16After running a major compaction, automatic minor compactions are no = longer triggered, frequently requiring you to manually run major = compactions on a routine basis." "DataStax does not recommend major compaction." So I'm unsure whether to start triggering manually these compactions=85 = I guess I'll have to experiment with it. Thanks! Andr=E9= --Apple-Mail=_66114344-FEF7-4B2A-BDC0-61366CC914CC Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 binhnv80@gmail.com> = wrote:
FYI: Repair does not remove = tombstones. To remove tombstones you need to run compaction.
If you have a lot of data then make sure you run compaction on all nodes = before running repair. We had a big trouble with our system regarding = tombstone and it took us long time to figure out the reason. It turned = out that repair process also transfers TTLed data (compaction is not = triggered yet) to the other nodes even that data was removed from the = other nodes in the compaction phase before that.


Aren't compactions triggered automatically? At least minor = compactions. Also, I read this in http://www.datastax.com/docs/1.1/operations/tuning#tuning-compaction :