why auto_bootstrap for all new nodes

[netflix]

why auto_bootstrap for all new nodes

[aryanet]

ok, according to this ticket https://issues.apache.org/jira/browse/CASSANDRA-2447 whether or not we set bootstrap to true, for a bare node, cassandra will set auto_bootstrap automatically to true if there are no other keyspace dirs than system. however in Priam instances we don't want this as each nodes token for new cluster is calculated, but it is not set in the configuration file when tuneCassandra is executed. I am puzzled on how to bring the new cluster up yet, and I keep digging, but if anyone knows, advice would be greatly appreciated.

[sorenvind]

I've seen the behavior that you describe, but the nodes will eventually converge and the remaining nodes will be able to start when the seed nodes have started up correctly (they will try to connect every 5 seconds until they are successful). Remember to clear the Cassandra data directories before restarting Priam/Cassandra - if you forget this, a saved token is used instead of the one that Priam generates. Also remember that your configuration cassandra.yaml must be first in the classpath in your Cassandra init.d script.

[aryanet]

oh dude! that last advice of yours was pure GOLD!!!!!! I owe you one.

[aryanet]

OK I have the cluster up and finally they all see each other with right ACLs set in security groups. Though, I feel there is an imbalance. I am going to file a ticket about that.