cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erik Onnen <>
Subject SSTable Corruption
Date Wed, 23 Mar 2011 21:59:59 GMT
After an upgrade from 0.7.3 to 0.7.4, we're seeing the following on
several data files:

ERROR [main] 2011-03-23 18:58:33,137 (line 235)
Corrupt sstable
Statistics.db, Data.db, Filter.db]; skipped
        at org.apache.cassandra.utils.EstimatedHistogram$EstimatedHistogramSerializer.deserialize(
        at org.apache.cassandra.db.ColumnFamilyStore.<init>(
        at org.apache.cassandra.db.ColumnFamilyStore.createColumnFamilyStore(
        at org.apache.cassandra.db.ColumnFamilyStore.createColumnFamilyStore(
        at org.apache.cassandra.db.Table.initCf(
        at org.apache.cassandra.db.Table.<init>(
        at org.apache.cassandra.service.AbstractCassandraDaemon.setup(
        at org.apache.cassandra.service.AbstractCassandraDaemon.activate(
        at org.apache.cassandra.thrift.CassandraDaemon.main(

Prior to the upgrade, there weren't problems opening these data files
with the exception that we were not able to bootstrap new nodes into
the ring due to what we believe was caused by CASSANDRA-2283. In
trying to fix 2283, we did run a scrub on this node.

With an RF of 3 in our ring, what are the implications of this? Specifically,

1) If the node is a natural endpoint for rows in the corrupt sstable,
will it simply not respond to requests for that row or will there be
2) Should a repair fix the broken sstable? This was my expectation
based on similar threads on the mailing list.
3) If #2 is correct and the repair did not fix the corrupt sstables
(which it did not), how should we proceed to repair the tables?


View raw message