Hi Robert. I'm thinking of upgrading hardware in place. Can you please elaborate a bit more on how to use the auto_bootstrap=false + hibernate repair technique?
Cheers! Carlos Alonso | Software Engineer | @calonso <https://twitter.com/calonso> On 6 January 2016 at 11:10, Herbert Fischer <herbert.fisc...@crossengage.io> wrote: > Hi, > > Thanks for the tip. > > I found that one keyspace was kinda corrupted. It was previously > scrubbed/deleted but there where files left in the servers, so it was in a > strange state. After removing it from the filesystem I was able to add the > new node to the cluster. Since this keyspace was in an unknown state, I > could not find it through the cfId from the error messages. > > best > > On 5 January 2016 at 22:33, Robert Coli <rc...@eventbrite.com> wrote: > >> On Tue, Jan 5, 2016 at 3:01 AM, Herbert Fischer < >> herbert.fisc...@crossengage.io> wrote: >> >>> We run a small Cassandra 2.2.0 cluster, with 5 nodes, on bare-metal >>> servers and we are going to replace those nodes with other nodes. I planned >>> to add all the new nodes first, one-by-one, and later remove the old ones, >>> one-by-one. >>> >> >> It sounds like your bootstraps are hanging. Your streams should restart >> after an hour, but probably you want to figure out why they're hanging... >> >> You can also use the auto_bootstrap=false+hibernate repair method for >> this process. That's probably what I'd do if I was upgrading the hardware >> of nodes in place. >> >> =Rob >> >> > > > > -- > Herbert Fischer | Senior IT Architect > CrossEngage GmbH (haftungsbeschränkt) | Julie-Wolfthorn-Straße 1 | 10115 > Berlin > > E-Mail: herbert.fisc...@crossengage.io > Web: www.crossengage.io > > Amtsgericht Berlin-Charlottenburg | HRB 169537 B > Geschäftsführer: Dr. Markus Wübben, Manuel Hinz | USt-IdNr.: DE301504202 >
