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 1EF37662D for ; Thu, 26 May 2011 18:51:40 +0000 (UTC) Received: (qmail 80088 invoked by uid 500); 26 May 2011 18:51:38 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 80066 invoked by uid 500); 26 May 2011 18:51:38 -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 80058 invoked by uid 99); 26 May 2011 18:51:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 May 2011 18:51:38 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jbellis@gmail.com designates 74.125.82.44 as permitted sender) Received: from [74.125.82.44] (HELO mail-ww0-f44.google.com) (74.125.82.44) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 May 2011 18:51:33 +0000 Received: by wwa36 with SMTP id 36so929787wwa.25 for ; Thu, 26 May 2011 11:51:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=6uLg74mFyplKYG9ZxWJMVRpWPUFemJzEag/Zi+BKloA=; b=dsXXf/HL91GOHsRptqaVYzgzeL1hBxjhtTF0+WaFZ7Qq5mAXg7vvHSIWg4tVkrJmGL 5SenL5ymAZndP9/OVzmiafvH86a2srhH8559BerhvFMr8JyLeDkYpBiRVobFB4jwLv6A vXL1rmwflthNF2Q6NKCpToT9UvBLAFXgmwugM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=pDgPa/FAedch1TZPa9esK6u0+pqbJs4YPx0ucCnQ5D2/8GTpjvVQpmHPY6V0TiWLKA 61v5jTJAG6vpMwIq6iCFZpDB3CUHF72MetiONpZKSqot0iw8R5kfNc1rmIm8MoY8sSEc l923v2TKgxAw9TNpt2aAkI2bWL2U5pUMDxlZc= Received: by 10.216.235.33 with SMTP id t33mr1190426weq.6.1306435872112; Thu, 26 May 2011 11:51:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.17.15 with HTTP; Thu, 26 May 2011 11:50:52 -0700 (PDT) In-Reply-To: <1511359117.207707.1306433375874.JavaMail.root@mail-1.01.com> References: <1277993186.199406.1306426075444.JavaMail.root@mail-1.01.com> <1511359117.207707.1306433375874.JavaMail.root@mail-1.01.com> From: Jonathan Ellis Date: Thu, 26 May 2011 13:50:52 -0500 Message-ID: Subject: Re: Forcing Cassandra to free up some space To: user@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 You'd have to call system.gc via JMX. https://issues.apache.org/jira/browse/CASSANDRA-2521 is open to address this, btw. On Thu, May 26, 2011 at 1:09 PM, Konstantin Naryshkin wrote: > I have a basic understanding of how Cassandra handles the file system > (flushes in Memtables out to SSTables, SSTables get compacted) and I > understand that old files are only deleted when a node is restarted, when > Java does a GC, or when Cassandra feels like it is running out of space. > > My question is, is there some way for us to hurry the process along? We have > a data that we do a lot of inserts into and then delete the data several > hours later. We would like it if we could free up disk space (since our > disks, though large, are shared with other applications). So far, the action > sequence to accomplish this is: > nodetoo flush -> nodetool repair -> nodetool compact -> ?? > > Is there a way for me to make (or even gently suggest to) Cassandra that it > may be a good time to free up some space? > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com