Hello again and sorry for the late response, Still having problems with upgrading from 2.1.8 to 2.1.9.
I decided to start the problematic nodes with "disk_failure_policy: best_effort" Currently running "nodetool scrub <keyspace> <table>" Then removing the corrupted sstables and planning to run repair afterwards This is way too many manual steps. I was wondering why not just removing the entire /var/lib/cassandra/data folder + commitlogs, restart the node again and wait to catch up Kind regards, George On Fri, Sep 25, 2015 at 12:01 AM, Robert Coli <rc...@eventbrite.com> wrote: > On Thu, Sep 24, 2015 at 3:00 PM, Robert Coli <rc...@eventbrite.com> wrote: > >> A node which has lost a SSTable also needs to be repaired immediately. >> > > Forgot to mention, you can repair via this technique : > > https://issues.apache.org/jira/browse/CASSANDRA-6961 > > =Rob > >
