Other way around: sstablekeys _only_ reads the index.
On Fri, Jun 11, 2010 at 4:51 PM, Brandon Williams wrote:
> On Fri, Jun 11, 2010 at 1:23 PM, Jonathan Ellis wrote:
>>
>> Hmm. That seems to be saying that sstable2json is using the index
>> file, and erroring out there the same way the Cassan
On Fri, Jun 11, 2010 at 1:23 PM, Jonathan Ellis wrote:
> Hmm. That seems to be saying that sstable2json is using the index
> file, and erroring out there the same way the Cassandra server does.
> So it doesn't necessarily mean the data files are corrupt.
I believe you can confirm this with sst
Hmm. That seems to be saying that sstable2json is using the index
file, and erroring out there the same way the Cassandra server does.
So it doesn't necessarily mean the data files are corrupt.
On Fri, Jun 11, 2010 at 11:20 AM, Lucas Di Pentima
wrote:
> Hello Jonathan,
>
> El 08/06/2010, a las 1
Hello Jonathan,
El 08/06/2010, a las 19:15, Jonathan Ellis escribió:
> Sounds like you had some bad hardware take down your index files.
> (Cassandra fsyncs them after writing them and before renaming them to
> being live, so if it's missing pieces then it's always been hardware
> at fault that I
El 09/06/2010, a las 04:31, Peter Schuller escribió:
>> I've had a server crash
>
> As jbellis points out there may be hardware issues, but if, in
> particular, the crash in question was a power outage a very common
> problem is running on a system which does not honor write barriers.
> Was it a
> I've had a server crash
As jbellis points out there may be hardware issues, but if, in
particular, the crash in question was a power outage a very common
problem is running on a system which does not honor write barriers.
Was it a power outage?
--
/ Peter Schuller
Sounds like you had some bad hardware take down your index files.
(Cassandra fsyncs them after writing them and before renaming them to
being live, so if it's missing pieces then it's always been hardware
at fault that I have seen.
You could try rebuilding your index files from the data files, but
Hello,
I've had a server crash, and after rebooting I cannot start the Cassandra
instance, it's a one-node cluster. I'm running cassandra 0.6.1 on Debian Linux
and jre 1.6.0_12.
Is my data lost, should I recreate the DB?
The error message is:
==
