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 BAD93F12E for ; Wed, 21 Aug 2013 14:34:37 +0000 (UTC) Received: (qmail 7284 invoked by uid 500); 21 Aug 2013 14:34:34 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 7187 invoked by uid 500); 21 Aug 2013 14:34:30 -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 7178 invoked by uid 99); 21 Aug 2013 14:34:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Aug 2013 14:34:29 +0000 X-ASF-Spam-Status: No, hits=-2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_HI,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [163.231.6.26] (HELO mailout2-trp.thomsonreuters.com) (163.231.6.26) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Aug 2013 14:34:22 +0000 Received: from trpusmneagrly02.int.westgroup.com (relay2 [163.231.22.113]) by mailout2-trp.thomsonreuters.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r7LEY1EX019040 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Wed, 21 Aug 2013 14:34:01 GMT Received: from EAGE-ERFPHUB02.ERF.thomson.com (EAGE-ERFPHUB02.erf.thomson.com [163.231.23.34]) by trpusmneagrly02.int.westgroup.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r7LEY0ed027360 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Wed, 21 Aug 2013 14:34:01 GMT Received: from UK2P-ERFMHUB02.ERF.thomson.com (10.29.4.13) by EAGE-ERFPHUB02.ERF.thomson.com (163.231.23.34) with Microsoft SMTP Server (TLS) id 14.2.342.3; Wed, 21 Aug 2013 09:34:00 -0500 Received: from UK2P-ERFMMBX15.ERF.thomson.com ([fe80::1876:69be:6909:9041]) by UK2P-ERFMHUB02.ERF.thomson.com ([::1]) with mapi id 14.02.0342.003; Wed, 21 Aug 2013 14:33:47 +0000 From: To: Subject: RE: Automatic tombstone compaction Thread-Topic: Automatic tombstone compaction Thread-Index: Ac6eeNlKMgRvZ5PvT+O0Ih7RracObQAAUYWAAAA6o3A= Date: Wed, 21 Aug 2013 14:33:46 +0000 Message-ID: <8DB9FC6F3E04544EB041210DCCB1E1710E3D5B29@UK2P-ERFMMBX15.ERF.thomson.com> References: <8DB9FC6F3E04544EB041210DCCB1E1710E3D5AFE@UK2P-ERFMMBX15.ERF.thomson.com> In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.29.4.139] Content-Type: multipart/alternative; boundary="_000_8DB9FC6F3E04544EB041210DCCB1E1710E3D5B29UK2PERFMMBX15ER_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_8DB9FC6F3E04544EB041210DCCB1E1710E3D5B29UK2PERFMMBX15ER_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, I ran upgradesstables as part of the Cassandra upgrade, before issuing the = CQL alter command. According to the docs, SizeTieredCompactionStrategy is fine (that is what I= used, and plan on continue using), and automatic tombstone compaction is a= vailable for it: http://www.datastax.com/documentation/cassandra/1.2/webhelp/index.html#cass= andra/operations/ops_about_config_compact_c.html I just had to include the 'class' in the alter statement, otherwise it woul= d not accept my command. Is that not right? Thanks, Tamas From: Haithem Jarraya [mailto:a-hjarraya@expedia.com] Sent: 21. august 2013 16:24 To: user@cassandra.apache.org Subject: Re: Automatic tombstone compaction Hi, do you mean LeveledCompactionStrategy? Also you will need to run nodetool upgradesstables [keyspace][cf_name] aft= er changing the compaction strategy. Thanks, Haithem Jarraya On 21 Aug 2013, at 15:15, tamas.foldesi@thomsonreuters.com wrote: Hi, After upgrading from 1.0 to 1.2, I wanted to make use of the automatic tomb= stone compaction feature, so using CQL3 I issued: ALTER TABLE versions WITH compaction =3D {'class' : 'SizeTieredCompactionSt= rategy', 'min_threshold' : 4, 'max_threshold' : 32, 'tombstone_compaction_i= nterval' : 1, 'tombstone_threshold' : '0.1'}; But I still see no trace that would suggest this works - we had 60G of data= with TTL=3D1week pushed a while ago to the test cluster, the majority of i= t should be expired & compacted away by now. Not sure if it is relevant, bu= t this old data is in one ~60G file + I have a few smaller files with lates= t data in them. Looking at JMX: DroppableTombstoneRatio =3D 0.892076544, which seems to bac= k my theory. Am I doing something wrong, or am I expecting the wrong thing? Thanks, Tamas --_000_8DB9FC6F3E04544EB041210DCCB1E1710E3D5B29UK2PERFMMBX15ER_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 <= /p>

I ran upgradesstables as = part of the Cassandra upgrade, before issuing the CQL alter command.

According to the docs, Si= zeTieredCompactionStrategy is fine (that is what I used, and plan on contin= ue using), and automatic tombstone compaction is available for it:

http://www.datastax.com/documentation/cassandra/1.2/webhelp/index.= html#cassandra/operations/ops_about_config_compact_c.html

I just had to include the= ‘class’ in the alter statement, otherwise it would not accept = my command.

Is that not right?

 <= /p>

Thanks,=

Tamas

 <= /p>

From: Haithem = Jarraya [mailto:a-hjarraya@expedia.com]
Sent: 21. august 2013 16:24
To: user@cassandra.apache.org
Subject: Re: Automatic tombstone compaction

 

Hi, 

 

do you mean LeveledCom= pactionStrategy?

 

Also you will need to run nodetool upgradesstables =  [keyspace][cf_name<= /span>] after changing the compaction strategy.

 

Thanks,

 

Haithem Jarraya=

On 21 Aug 2013, at 15:15, tamas.foldesi@thomsonreuters.com wrote:



Hi,

 

After upgrading from 1.0 to 1.2, I want= ed to make use of the automatic tombstone compaction feature, so using CQL3= I issued:

 

ALTER TABLE versions WIT= H compaction =3D {'class' : 'SizeTieredCompactionStrategy', 'min_threshold'= : 4, 'max_threshold' : 32, 'tombstone_compaction_interval' : 1, 'tombstone_threshold' : '0.1'};

 

But I still see no trace that would sug= gest this works – we had 60G of data with TTL=3D1week pushed a while = ago to the test cluster, the majority of it should be expired & compacted away by now. Not sure if it is relevant, but this old data is in= one ~60G file + I have a few smaller files with latest data in them.

Looking at JMX: DroppableTombstoneRatio= =3D 0.892076544, which seems to back my theory.

Am I doing something wrong, or am I exp= ecting the wrong thing?

 

Thanks,

Tamas

 

 

--_000_8DB9FC6F3E04544EB041210DCCB1E1710E3D5B29UK2PERFMMBX15ER_--