Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 38336 invoked from network); 13 Jul 2010 16:11:21 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 13 Jul 2010 16:11:21 -0000 Received: (qmail 45034 invoked by uid 500); 13 Jul 2010 16:11:20 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 44997 invoked by uid 500); 13 Jul 2010 16:11:19 -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 44989 invoked by uid 99); 13 Jul 2010 16:11:19 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Jul 2010 16:11:19 +0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.216.179] (HELO mail-qy0-f179.google.com) (209.85.216.179) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Jul 2010 16:11:12 +0000 Received: by qyk2 with SMTP id 2so4993880qyk.10 for ; Tue, 13 Jul 2010 09:10:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.224.119.20 with SMTP id x20mr8855404qaq.249.1279037451542; Tue, 13 Jul 2010 09:10:51 -0700 (PDT) Received: by 10.229.224.141 with HTTP; Tue, 13 Jul 2010 09:10:51 -0700 (PDT) In-Reply-To: References: Date: Tue, 13 Jul 2010 09:10:51 -0700 Message-ID: Subject: Re: Question regarding consistency and deletion From: Benjamin Black To: user@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Jul 13, 2010 at 5:47 AM, Samuru Jackson wrote: > Thanks for the links. > > Actually it is pretty easy to catch those tombstoned keys on the > client side. However, in certain applications it can generate some > additional overhead on the network. > > I think it would be nice to have a forced garbage collection in the > API. This would IMHO ease to write Unit-Tests. You can, via JMX. Given how painful frequent major compactions can be, I don't see value in putting it in the Thrift API. b