+1
Scaling up & down can also take some time (multiple days even) if the nodes
in the cluster hold a lot of data. The process has a performance impact on
the cluster, as the rest of the cluster must stream data to the new nodes,
or stream data away from the decommissioning nodes, also usually lead
On Tue, Oct 17, 2017 at 7:40 AM, Jeff Jirsa wrote:
> Just to expand on this:
>
> In an asg environment, you could have an autoscaling event to expand or
> shrink the cluster and multiple nodes terminate at the same time. Your
> userdata or your AMI would have to know how to find the cluster, know
Just to expand on this:
In an asg environment, you could have an autoscaling event to expand or shrink
the cluster and multiple nodes terminate at the same time. Your userdata or
your AMI would have to know how to find the cluster, know how many instances
were down and what the target size was,
I wouldn't recommend putting your Cassandra nodes in an ASG. Scaling
production Cassandra clusters can be a tricky process that should be done
manually. There are a lot of things that can go wrong if you aren't
watching/controlling the process.
Terraform is a good option for automating complex AWS
How can we solve EIP allocation using APIs for multiple nodes that are in
one ASG? What are the config management tools that you are referring to?
On Mon, Oct 16, 2017 at 9:23 PM, kurt greaves wrote:
> AWS API's provide the functionality to allocate and associate elastic IPs
> to instances. Ge
AWS API's provide the functionality to allocate and associate elastic IPs
to instances. Generally the API's aren't pretty but they work. What issues
are you having? If it's a configuration problem there are a variety of
config management tools that you can use to populate the yaml/env files
with th
