If you've been dropping and recreating tables with the same name, you might be seeing this: https://issues.apache.org/jira/browse/CASSANDRA-6525
On Tue, Jun 10, 2014 at 12:19 PM, Robert Coli <rc...@eventbrite.com> wrote: > On Tue, Jun 10, 2014 at 7:31 AM, Jeremy Jongsma <jer...@barchart.com> > wrote: > >> I'm in the process of migrating data over to cassandra for several of our >> apps, and a few of the schemas use secondary indexes. Four times in the >> last couple months I've run into a corrupted sstable belonging to a >> secondary index, but have never seen this on any other sstables. When it >> happens, any query against the secondary index just hangs until the node is >> fixed. It's making me a bit nervous about using secondary indexes in >> production. >> > > > http://mail-archives.apache.org/mod_mbox/incubator-cassandra-user/201405.mbox/%3CCAEDUwd1i2BwJ-PAFE1qhjQFZ=qz2va_vxwo_jdycms8evkb...@mail.gmail.com%3E > > I don't know if this particular issue is known and/or fixed upstream, but > FWIW/FYI! > > =Rob > -- Tyler Hobbs DataStax <http://datastax.com/>
