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 gatman1001@gmail.com designates
 209.85.212.51 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAEDUwd2MDc=0VUwbybWKq=AG5CY8AcCNK-ma0uDHLFM99Qexkw@mail.gmail.com>
References: <93fa6a475304c9d60e1f9a321c76a2b7@team.enercast.de>
	<CAEDUwd2MDc=0VUwbybWKq=AG5CY8AcCNK-ma0uDHLFM99Qexkw@mail.gmail.com>
Date: Wed, 3 Jul 2013 11:10:44 -0600
Message-ID: 
 <CAEfSkOqHpeAnPZSpfPCgaCs3b6XbwD6Ahpkcwqmf0r4=vJ7uzw@mail.gmail.com>
Subject: Re: CorruptBlockException - recover?
From: Glenn Thompson <gatman1001@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=089e0153688cc5b11d04e09e8a30

--089e0153688cc5b11d04e09e8a30
Content-Type: text/plain; charset=ISO-8859-1

For what its worth.  I did this when I had this problem.  It didn't work
out for me.  Perhaps I did something wrong.


On Wed, Jul 3, 2013 at 11:06 AM, Robert Coli <rcoli@eventbrite.com> wrote:

> On Wed, Jul 3, 2013 at 7:04 AM, ifjke <j.kesten@enercast.de> wrote:
>
>> I found that one of my cassandra nodes died recently (machine hangs). I
>> restarted the node an run a nodetool repair, while running it has thrown a
>> org.apache.cassandra.io.**compress.**CorruptBlockException. Is there any
>> way to recover from this? Or would it be best to delete the nodes contents
>> and bootstrap it again?
>>
>
> If you "scrub" this SSTable (either with the online or offline version of
> "scrub") it will remove the corrupt data and re-write the rest of the
> SSTable which isn't corrupt into a new SSTable. That is probably safer for
> your data than deleting the entire set of data on this replica. When that's
> done, restart the repair.
>
> =Rob
>

--089e0153688cc5b11d04e09e8a30
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">For what its worth. =A0I did this when I had this problem.=
 =A0It didn&#39;t work out for me. =A0Perhaps I did something wrong.</div><=
div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Wed, Jul 3,=
 2013 at 11:06 AM, Robert Coli <span dir=3D"ltr">&lt;<a href=3D"mailto:rcol=
i@eventbrite.com" target=3D"_blank">rcoli@eventbrite.com</a>&gt;</span> wro=
te:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"im">On Wed, J=
ul 3, 2013 at 7:04 AM, ifjke <span dir=3D"ltr">&lt;<a href=3D"mailto:j.kest=
en@enercast.de" target=3D"_blank">j.kesten@enercast.de</a>&gt;</span> wrote=
:<br>
</div><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div class=3D"i=
m">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I found that one of my cassandra nodes died =
recently (machine hangs). I restarted the node an run a nodetool repair, wh=
ile running it has thrown a <a href=3D"http://org.apache.cassandra.io" targ=
et=3D"_blank">org.apache.cassandra.io</a>.<u></u>compress.<u></u>CorruptBlo=
ckException. Is there any way to recover from this? Or would it be best to =
delete the nodes contents and bootstrap it again?<br>

</blockquote><div><br></div></div><div>If you &quot;scrub&quot; this SSTabl=
e (either with the online or offline version of &quot;scrub&quot;) it will =
remove the corrupt data and re-write the rest of the SSTable which isn&#39;=
t corrupt into a new SSTable. That is probably safer for your data than del=
eting the entire set of data on this replica. When that&#39;s done, restart=
 the repair.</div>

<div><br></div><div>=3DRob</div></div></div></div>
</blockquote></div><br></div>

--089e0153688cc5b11d04e09e8a30--