Sylvain, thanks for the quick response, and you are correct: there is an empty index file. I removed the file and tried to start it up. Now Cassandra is reporting corrupt sstables. Does this mean I can't just simply back up var/lib directory (use snapshots instead) ? We don't have much data right now so I thought it'd be easier to back up the entire directory.
I think that could be triggered if you have a 0 bytes index file forOn Thu, May 5, 2011 at 8:38 PM, Wenjun Che <firstname.lastname@example.org> wrote:
> I have a one node cluster (refresh install from 0.7.4 and upgraded to 0.7.5
> last week). The data is being backed up by a cron job that periodically
> tar/gzip entire
> var/lib directory. when I tested the backup by restoring the last tar file,
> I am seeing the following exception:
> DEBUG 13:45:37,830 Load statistics for
> ERROR 13:45:37,832 Exception encountered during startup.
> at org.apache.cassandra.db.Table.initCf(Table.java:308)
> at org.apache.cassandra.db.Table.<init>(Table.java:245)
> at org.apache.cassandra.db.Table.open(Table.java:106)
> Exception encountered during startup.
> I checked few other earlier backup tar files and they seem to be fine. Can
> this be caused by the way I am backing it up?
instance, so if you had one such
index file in the backup, that could be a problem.