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 64C4410EA6 for ; Sat, 21 Sep 2013 01:56:31 +0000 (UTC) Received: (qmail 51479 invoked by uid 500); 21 Sep 2013 01:56:28 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 51455 invoked by uid 500); 21 Sep 2013 01:56:28 -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 51447 invoked by uid 99); 21 Sep 2013 01:56:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 21 Sep 2013 01:56:28 +0000 X-ASF-Spam-Status: No, hits=2.4 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of java8964@hotmail.com designates 65.55.90.166 as permitted sender) Received: from [65.55.90.166] (HELO snt0-omc3-s27.snt0.hotmail.com) (65.55.90.166) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 21 Sep 2013 01:56:21 +0000 Received: from SNT149-W9 ([65.55.90.136]) by snt0-omc3-s27.snt0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 20 Sep 2013 18:56:00 -0700 X-TMN: [l93W0dTWgEc+nkv+U5bKTX2ORxfHl4LZ] X-Originating-Email: [java8964@hotmail.com] Message-ID: Content-Type: multipart/alternative; boundary="_3568c319-e8ba-4011-9949-a39711a21128_" From: java8964 java8964 To: "user@cassandra.apache.org" Subject: Is it possible to control the sstable file size in incremental backup or snapshot Date: Fri, 20 Sep 2013 21:56:00 -0400 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 21 Sep 2013 01:56:00.0639 (UTC) FILETIME=[B8AD78F0:01CEB66D] X-Virus-Checked: Checked by ClamAV on apache.org --_3568c319-e8ba-4011-9949-a39711a21128_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi=2C The current our production is using Cassandra 1.0=2C and will upgrade to 1.= 1 next week. I noticed the snapshot and incremental backup sstable files size generated = from our production environment vary dramatically. Some files can be hundre= ds of M=2C or even close to G=2C but a lot of files are even less than 1k b= ytes=2C especially in the incremental backup. Is there a way to control the size of SSTable files generated in the snapsh= ot or incremental backup? I am talking about one column family. Ideally fo= r this column family=2C I would like to make every SSTable files around 500= M to 1G. Thanks = --_3568c319-e8ba-4011-9949-a39711a21128_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi=2C

The cur= rent our production is using Cassandra 1.0=2C and will upgrade to 1.1 next = week.

I noticed the snapshot and incremental backu= p sstable files size generated from our production environment vary dramati= cally. Some files can be hundreds of M=2C or even close to G=2C but a lot o= f files are even less than 1k bytes=2C especially in the incremental backup= .

Is there a way to control the size of SSTable fi= les generated in the snapshot or incremental backup? =3BI am talking a= bout one column family. Ideally for this column family=2C I would like to m= ake every SSTable files around 500M to 1G.

Thanks<= /div>

= --_3568c319-e8ba-4011-9949-a39711a21128_--