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 210FB9272 for ; Mon, 19 Sep 2011 16:27:44 +0000 (UTC) Received: (qmail 32595 invoked by uid 500); 19 Sep 2011 16:27:41 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 32571 invoked by uid 500); 19 Sep 2011 16:27:41 -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 32560 invoked by uid 99); 19 Sep 2011 16:27:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Sep 2011 16:27:41 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [74.125.82.170] (HELO mail-wy0-f170.google.com) (74.125.82.170) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Sep 2011 16:27:32 +0000 Received: by wyg8 with SMTP id 8so7064109wyg.29 for ; Mon, 19 Sep 2011 09:27:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.80.1 with SMTP id j1mr2012953wee.44.1316449632413; Mon, 19 Sep 2011 09:27:12 -0700 (PDT) Sender: scode@scode.org Received: by 10.216.203.148 with HTTP; Mon, 19 Sep 2011 09:27:12 -0700 (PDT) X-Originating-IP: [94.234.170.38] In-Reply-To: References: Date: Mon, 19 Sep 2011 18:27:12 +0200 X-Google-Sender-Auth: zfjSH8g-xghFsO7LVlmAmSEUddg Message-ID: Subject: Re: cassandra crashed while repairing, leave node size X3 From: Peter Schuller To: user@cassandra.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org > In my tests I have seen repair sometimes take a lot of space (2-3 times), > cleanup did not clean it, the only way I could clean that was using major > compaction. https://issues.apache.org/jira/browse/CASSANDRA-2816 (follow links to other jiras) https://issues.apache.org/jira/browse/CASSANDRA-2699 And yes to the one who asked: 'cleanup' only removes data that is not supposed to be on the node; repair transferes data that *should* be on the node, so only a compaction will cut down the size after a repair induced spike of load (data size). -- / Peter Schuller (@scode on twitter)