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 CCC74D525 for ; Thu, 8 Nov 2012 18:12:59 +0000 (UTC) Received: (qmail 71725 invoked by uid 500); 8 Nov 2012 18:12:57 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 71701 invoked by uid 500); 8 Nov 2012 18:12:57 -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 71640 invoked by uid 99); 8 Nov 2012 18:12:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Nov 2012 18:12:54 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of btoddb@gmail.com designates 209.85.219.44 as permitted sender) Received: from [209.85.219.44] (HELO mail-oa0-f44.google.com) (209.85.219.44) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Nov 2012 18:12:48 +0000 Received: by mail-oa0-f44.google.com with SMTP id n5so3410720oag.31 for ; Thu, 08 Nov 2012 10:12:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=jp1vPjRF8/dMgqPVE4vMcRxFDAZtqIEFyvRUJiu9Es4=; b=NCDWiwDGHv4fQDVczwc3YXa6k8w/5PyVwaukxFeZJpoKOAFcBNmfA9I7atrSR//Z5H fMHhOu05p/GPIi/qA8wpyNM9vWOhgqgFhhQej5LSBJFAkWpG62pGPuYrsi6p4+TXg6ic aCBZKvk1cNXVghXOpjiCCLiPjDzKaSTQl6S7ceLYkKjTtmmI0FojX8pYSv4VjVxiEGjs MN5jK+JG+6//ppPEjWK6jx4Z50jHVqyXFe4e8rQOTTr058zzVHvzLOfvPTOshD7lWPqL 5RjfIkQbBApNAilMrpRGqC9+5cLLTcMbQmFa6xd8BknwxwxFEl0mjdXEXRQEheGFyfg0 /S0Q== MIME-Version: 1.0 Received: by 10.60.31.135 with SMTP id a7mr5512291oei.26.1352398347717; Thu, 08 Nov 2012 10:12:27 -0800 (PST) Received: by 10.182.171.8 with HTTP; Thu, 8 Nov 2012 10:12:27 -0800 (PST) Date: Thu, 8 Nov 2012 10:12:27 -0800 Message-ID: Subject: leveled compaction and tombstoned data From: "B. Todd Burruss" To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=e89a8fb1f59a1c4a8a04cdffc7b8 X-Virus-Checked: Checked by ClamAV on apache.org --e89a8fb1f59a1c4a8a04cdffc7b8 Content-Type: text/plain; charset=ISO-8859-1 we are having the problem where we have huge SSTABLEs with tombstoned data in them that is not being compacted soon enough (because size tiered compaction requires, by default, 4 like sized SSTABLEs). this is using more disk space than we anticipated. we are very write heavy compared to reads, and we delete the data after N number of days (depends on the column family, but N is around 7 days) my question is would leveled compaction help to get rid of the tombstoned data faster than size tiered, and therefore reduce the disk space usage? thx --e89a8fb1f59a1c4a8a04cdffc7b8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable we are having the problem where we have huge SSTABLEs with tombstoned data = in them that is not being compacted soon enough (because size tiered compac= tion requires, by default, 4 like sized SSTABLEs). =A0this is using more di= sk space than we anticipated.

we are very write heavy compared to reads, and we delete the= data after N number of days (depends on the column family, but N is around= 7 days)

my question is would leveled compaction h= elp to get rid of the tombstoned data faster than size tiered, and therefor= e reduce the disk space usage?

thx


--e89a8fb1f59a1c4a8a04cdffc7b8--