incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <jbel...@gmail.com>
Subject Re: SSTable Corruption
Date Fri, 25 Mar 2011 03:34:27 GMT
Yes, Statistics is convenient because as part of supporting old 0.6
data Cassandra will just build it if it's not there.

Technically you can rebuild filter and index too but it's not automatic.

It looks like when we added statistics we didn't make sure to fsync it
when we fsync the other components.  Patch attached to
https://issues.apache.org/jira/browse/CASSANDRA-2382.

On Thu, Mar 24, 2011 at 5:47 PM, Thibaut Britz
<thibaut.britz@trendiction.com> wrote:
> Just accidently hard resetet a node running 0.7.2 (with some patches from
> 0.7.3) and had the same problem.
>
> I'm a little hesitating upgrading to 0.7.4
>
> Can I always delete the Statistics.db without any data loss?
>
> Thibaut
>
>
> On Thu, Mar 24, 2011 at 1:37 AM, Brandon Williams <driftx@gmail.com> wrote:
>>
>> On Wed, Mar 23, 2011 at 6:52 PM, Erik Onnen <eonnen@gmail.com> wrote:
>>>
>>> Thanks, so is it the "[Index.db, Statistics.db, Data.db, Filter.db];
>>> skipped" that indicates it's in Statistics? Basically I need a way to
>>> know if the same is true of all the other tables showing this issue.
>>
>> It's theĀ at
>> org.apache.cassandra.utils.EstimatedHistogram$EstimatedHistogramSerializer.deserialize(EstimatedHistogram.java:207)
>> that clued me in.
>> -Brandon
>



-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com

Mime
View raw message