Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 66497 invoked from network); 22 Feb 2011 17:22:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 22 Feb 2011 17:22:08 -0000 Received: (qmail 62636 invoked by uid 500); 22 Feb 2011 17:22:06 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 62441 invoked by uid 500); 22 Feb 2011 17:22:03 -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 62433 invoked by uid 99); 22 Feb 2011 17:22:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Feb 2011 17:22:02 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rcoli@digg.com designates 209.85.210.172 as permitted sender) Received: from [209.85.210.172] (HELO mail-iy0-f172.google.com) (209.85.210.172) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Feb 2011 17:21:57 +0000 Received: by iyj8 with SMTP id 8so2053287iyj.31 for ; Tue, 22 Feb 2011 09:21:36 -0800 (PST) MIME-Version: 1.0 Received: by 10.42.196.65 with SMTP id ef1mr47058icb.357.1298395296421; Tue, 22 Feb 2011 09:21:36 -0800 (PST) Received: by 10.231.192.80 with HTTP; Tue, 22 Feb 2011 09:21:36 -0800 (PST) In-Reply-To: References: Date: Tue, 22 Feb 2011 09:21:36 -0800 Message-ID: Subject: Re: Help with Error on reading sstable From: Robert Coli To: user@cassandra.apache.org Cc: Jake Maizel Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Tue, Feb 22, 2011 at 4:32 AM, Jake Maizel wrote: > I'm getting this error after a space problem caused issues during a > repair operation on one of six nodes in our cluster: > ... > I am thinking that there was a failure with writing out an SSTable > because of space and now its corrupt. If this is the case, the easiest way to get this node back up is to simply remove the corrupt SSTable from the datadir temporarily and to try to recover its data offline. > Also, the repair caused a huge amount of disk to be used and therefore ra= n out. https://issues.apache.org/jira/browse/CASSANDRA-1674 > Currently, is there a way to clear space in this situation? =A0Would runn= ing a clean up > help? If your disk is still full, it's going to be difficult for you to complete a cleanup compaction. However if you are able to do so, I believe it would in fact help. > Running ver 0.6.6. 0.6.6 does not contain the patch from : https://issues.apache.org/jira/browse/CASSANDRA-1676 And is therefore highly unlikely to successfully repair except by accident. If your intent is to successfully repair, I strongly suggest either upgrading to 0.6.8 (which contains the imo critical 1676, but not the important-but-not-critical-1674) or just patching 1676 and 1674 into 0.6.6. =3DRob