See also: https://issues.apache.org/jira/browse/CASSANDRA-11163
On Wed, Aug 23, 2017 at 11:07 AM, Jeff Jirsa <jji...@gmail.com> wrote: > Typically if that sstable is damaged you'd see some sort of message. If > you recently changed bloom filter or index intervals for that table, it may > be silently rebuilding the other components of that sstable. Does cassandra > exit or does it just keep churning away? > > > > On Wed, Aug 23, 2017 at 10:20 AM, Mark Furlong <mfurl...@ancestry.com> > wrote: > >> I had an existing node go down. I don’t know the cause of this. I am >> starting Cassandra and I can see in the log that it starts and then hangs >> on the opening of an sstable. Is there anything I can do to fix the sstable? >> >> >> >> I’m on OSC 2.1.12. >> >> >> >> *Thanks in advance,* >> >> *Mark Furlong* >> >> Sr. Database Administrator >> >> *mfurl...@ancestry.com <mfurl...@ancestry.com>* >> M: 801-859-7427 <(801)%20859-7427> >> >> O: 801-705-7115 <(801)%20705-7115> >> >> 1300 W Traverse Pkwy >> >> Lehi, UT 84043 >> >> >> >> >> >> [image: http://c.mfcreative.com/mars/email/shared-icon/sig-logo.gif] >> >> >> >> >> > >
