Re: Rapid scaleup of cassandra nodes with snapshots and initial_token in the yaml

Ok, so vnodes are random assignments under normal circumstances (I'm in 2.1.x, I'm assuming a derivative approach was in the works that would avoid some hot node aspects of random primary range assingment for new nodes once you had one or two or three in a cluster). So... couldn't I just

Re: Rapid scaleup of cassandra nodes with snapshots and initial_token in the yaml

Thanks. Yeah, it appears this would only be doable if we didn't have vnodes and used old single token clusters. I guess Priam has something where you increase the cluster by whole number multiples. Then there's the issue of doing quorum read/writes if there suddenly is a new replica range with

Re: Rapid scaleup of cassandra nodes with snapshots and initial_token in the yaml

Ben did a talk that might have some useful information. It's much more complicated with vnodes though and I doubt you'll be able to get it to be as rapid as you'd want. sets up schema to match This shouldn't be

Re: Rapid scaleup of cassandra nodes with snapshots and initial_token in the yaml

Short answer is "yes, with caveats". I recall a talk about this from Cassandra Summit ~2014 or so. I THINK it was from Instaclustr, but I'm not positive. Maybe Ben or Kurt or someone over there has more info (if it really was them)? On Wed, Feb 14, 2018 at 9:40 AM, Carl Mueller

Re: Rapid scaleup of cassandra nodes with snapshots and initial_token in the yaml

Or could we do a rapid clone to a new cluster, then add that as another datacenter? On Wed, Feb 14, 2018 at 11:40 AM, Carl Mueller wrote: > https://stackoverflow.com/questions/48776589/cassandra- >