Re: unrepairable sstable data rows

2011-04-11 Thread aaron morton
FYI, I was chatting with Dominic Williams on IRC yesterday, he had an 0.7.4 install with the same problem see error stack here http://pastebin.com/YasPtEYj He has not run nodetool scrub but I think it the 0.7.4 install had been there a while so I the data file may have been fresh. Aaron On 1

Re: unrepairable sstable data rows

2011-04-11 Thread Sylvain Lebresne
Remove main-f-5-{Index|Filter|Statistics}.db files. They make no sense without a Data file and Cassandra always make sure it removes those before the Data file (that while it gets confused if it finds one of those file without a data file). Note that your error was with the sstable main-f-232-Data

Re: unrepairable sstable data rows

2011-04-11 Thread Jonathan Colby
Thanks for the answer Aaron. There are Data, Index, Filter, and Statistics files associated with SSTables. What files must be physically moved/deleted? I tried just moving the Data file and Cassandra would not start. I see this exception: WARN [WrapperSimpleAppMain] 2011-04-11 12:04:23,23

Re: unrepairable sstable data rows

2011-04-10 Thread aaron morton
The WARN messages are the "emergency pressure valve" kicking in, search for that test in conf/cassandra.yaml. These are settings to reduce the chance of going OOM. It means you should take a look at your memtable and cache settings as you are getting close to running out of memory. Jonathan or

unrepairable sstable data rows

2011-04-10 Thread Jonathan Colby
It appears we have several unserializable or unreadable rows. These were not fixed even after doing a "scrub" on all nodes - even though the scrub seemed to have completed successfully. I trying to fix these by doing a "repair", but these exceptions are thrown exactly when doing a repair.