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 DFC4651A9 for ; Thu, 12 May 2011 18:31:18 +0000 (UTC) Received: (qmail 7122 invoked by uid 500); 12 May 2011 18:31:16 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 7099 invoked by uid 500); 12 May 2011 18:31:16 -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 7091 invoked by uid 99); 12 May 2011 18:31:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 May 2011 18:31:16 +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 sanjeev@locomatix.com designates 209.85.216.44 as permitted sender) Received: from [209.85.216.44] (HELO mail-qw0-f44.google.com) (209.85.216.44) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 May 2011 18:31:10 +0000 Received: by qwc23 with SMTP id 23so1230018qwc.31 for ; Thu, 12 May 2011 11:30:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.224.213.194 with SMTP id gx2mr490022qab.255.1305225049092; Thu, 12 May 2011 11:30:49 -0700 (PDT) Received: by 10.224.45.194 with HTTP; Thu, 12 May 2011 11:30:49 -0700 (PDT) Date: Thu, 12 May 2011 11:30:49 -0700 Message-ID: Subject: Commitlog Disk Full From: Sanjeev Kulkarni To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=20cf3005149867326d04a318633e --20cf3005149867326d04a318633e Content-Type: text/plain; charset=ISO-8859-1 Hey guys, I have a ec2 debian cluster consisting of several nodes running 0.7.5 on ephimeral disks. These are fresh installs and not upgrades. The commitlog is set to the smaller of the disks which is around 10G in size and the datadir is set to the bigger disk. The config file is basically the same as the one supplied by the default installation. Our applications write to the cluster. After about a day of writing we started noticing the commitlog disk filling up. Soon we went over the disk limit and writes started failing. At this point we stopped the cluster. Over the course of the day we inserted around 25G of data. Our columns values are pretty small. I understand that cassandra periodically cleans up the commitlog directories by generating sstables in datadir. Is there any way to speed up this movement from commitog to datadir? Thanks! --20cf3005149867326d04a318633e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hey guys,

I have a ec2 debian cluster consisting of several nodes runni= ng 0.7.5 on ephimeral disks.=A0

These are fresh installs and not = upgrades.=A0

The commitlog is set to the smaller of the disks whi= ch is around 10G in size and the datadir is set to the bigger disk.

The config file is basically the same as the one supplied by the defau= lt installation.

Our applications write t= o the cluster.=A0After about a day of writing we started noticing the commi= tlog disk filling up. Soon we went over the disk limit and writes started f= ailing. At this point we stopped the cluster.

Over the course of the day we inserted around 25G of data. Our columns= values are pretty small.=A0

I understand that cassandra periodic= ally cleans up the commitlog directories by generating sstables in datadir.= Is there any way to speed up this movement from commitog to datadir?=A0

Thanks!

--20cf3005149867326d04a318633e--