Agreed. If your data model is good and no major read latencies due to little or
no data skew, wide partitions, or tombstones, you can literally scale linearly.
You could also consider having a plan in which you ramp up as the traffic
increases.
Rahul Singh
Chief Executive Officer
m 202.905.2818
Anant Corporation
1010 Wisconsin Ave NW, Suite 250
Washington, D.C. 20007
We build and manage digital business technology platforms.
On Aug 14, 2018, 6:31 PM -0500, kurt greaves , wrote:
> Not a great idea to make config changes without testing. For a lot of changes
> you can make the change on one node and measure of three is an improvement
> however.
>
> You'd probably be best to add nodes (double should be sufficient), do tuning
> and testing afterwards, and then decommission a few nodes if you can.
>
> > On Wed., 15 Aug. 2018, 05:00 Abdul Patel, wrote:
> > > Currently our cassandra prod is 18 node 3 dc cluster and application does
> > > 55 million reads per day and want to add load and make it 90 millon reads
> > > per day.they need a guestimate of resources which we need to bump without
> > > testing ..on top of my head we can increase heap and native trasport
> > > value ..any other paramters i should be concern?
