looks like a restart of cassandra and a "nodetool compact" fixed this…
On Wed, Jul 16, 2014 at 6:45 PM, Kevin Burton <bur...@spinn3r.com> wrote: > this is really troubling… > > I have a "ghost" table. I dropped it.. but it's not going away. > > (Cassandra 2.0.8 btw) > > I ran a 'drop table' on it.. then a 'describe tables' shows that it's not > there. > > However, when I recreated it, with a new schema, all operations on it > failed. > > Looking at why… it seems that cassandra had some old SSTables that I > imagine are no longer being used but are now in an inconsistent state? > > This is popping up in the system.log: > > Caused by: java.lang.RuntimeException: java.io.FileNotFoundException: > /d0/cassandra/data/blogindex/content_idx_source_hashcode/blogindex-content_idx_source_hashcode-jb-1447-Data.db > (No such file or directory) > > so I think what happened… is that the original drop table, failed, and > then left things in an inconsistent state. > > I tried a nodetool repair and a nodetool compact… those fail on the > same java.io.FileNotFoundException … I moved the directories out of the > way, same failure issue. > > … any advice on resolving this? > > -- > > Founder/CEO Spinn3r.com > Location: *San Francisco, CA* > blog: http://burtonator.wordpress.com > … or check out my Google+ profile > <https://plus.google.com/102718274791889610666/posts> > <http://spinn3r.com> > > -- Founder/CEO Spinn3r.com Location: *San Francisco, CA* blog: http://burtonator.wordpress.com … or check out my Google+ profile <https://plus.google.com/102718274791889610666/posts> <http://spinn3r.com>
