If fast bootstrapping is a high priority then using less dense nodes is the
tradeoff.
For example, rather than having 5 nodes with 3TB you could deploy 15 (less
powerful) nodes with 1TB each. Your cluster will have higher overall disk
throughput which would allow you to increase the stream
It sounds like you’re asking how to bootstrap without paying the cost of
bootstrapping :)
If you want to scale out, you’ll need to deal with the time it takes. You
can’t add a node and have it up in 15 minutes, if you’re running 3 TB it’ll
take a while. The exact amount of time depends
Adding more compute power means again vertical scaling. I understand this
is one method to handle the load in case of increasing demand. But it
doesn't match with philosophy of Cassandra for horizontal scaling. Hitting
capacity cannot be restricted to only compute power.
Also in case of node
Hi Anshu
For quick scaling, we’ve had success with an approach of scaling up the
compute capacity (attached to EBS) rather than scaling out with more nodes
in order to provide relatively quick scale up/down capability. The approach
is implemented as part of our managed service but the concept is
Cassandra supports elastic scalability - meaning on demand we can increase
or decrease #of nodes as per scaling demand from the application.
Let's consider we have 5 node cluster and each node has data pressure of
about 3 TB.
Now as per sudden load, we want to add 1 node in the cluster as
