Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of rcoli@eventbrite.com designates
 209.85.216.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CDC4D029.292CD%Dean.Hiller@nrel.gov>
References: <CDC4D029.292CD%Dean.Hiller@nrel.gov>
Date: Fri, 24 May 2013 09:54:23 -0700
Message-ID: 
 <CAEDUwd24twH=O2RNr+oJCO04fFpwC4Eec96m1zEnuL-_PQs0oQ@mail.gmail.com>
Subject: Re: corrupt sstable
From: Robert Coli <rcoli@eventbrite.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Fri, May 24, 2013 at 7:07 AM, Hiller, Dean <Dean.Hiller@nrel.gov> wrote:
> We have a corrupt sstable databus5-nreldata-ib-36763-Data.db.  How do we =
safely blow this away?  (and then we would run repair to make sure all data=
 is still there)=85
>
> Can we just move the file out from under cassandra?  (or would cassandra =
freak out?)

You can check via lsof whether the file is open by cassandra, but if
it is corrupt it was probably not successfully opened. If it's not
open by cassandra, you can do whatever you want to it. Actually if
it's open by cassandra you can also do whatever you want to, except
that whatever you do won't happen until cassandra releases its
filehandle.

=3DRob