1 million write per hour is around 250 writes per second .its easily achievable with 3 nodes .make sure that you have a good gc tuning and compaction tunings.
Sent from my iPhone On Dec 26, 2016, at 1:27 PM, Ney, Richard <richard....@aspect.com<mailto:richard....@aspect.com>> wrote: My company has a product we're about to deploy into AWS with Cassandra setup as a two 3 node clusters in two availability zones (m4.2xlarge with 2 500GB EBS volumes per node). We're doing over a million writes per hour with the cluster setup with R-2 and local quorum writes. We run successfully for several hours before Cassandra goes into the weeds and we start getting write timeouts to the point we must kill the Cassandra JVM processes to get the Cassandra cluster to restart. I keep raising to my upper management that the cluster is severely undersized but management is complaining that setting up 12 nodes is too expensive and to change the code to reduce load on Cassandra. So, the main question is "Is there any hope of success with a 3 node DC setup of Cassandra in production or are we on a fool's errand?" RICHARD NEY TECHNICAL DIRECTOR, RESEARCH & DEVELOPMENT +1 (978) 848.6640 WORK +1 (916) 846.2353 MOBILE UNITED STATES richard....@aspect.com<mailto:richard....@aspect.com> aspect.com<http://www.aspect.com/> [mailSigLogo-rev.jpg] This email (including any attachments) is proprietary to Aspect Software, Inc. and may contain information that is confidential. If you have received this message in error, please do not read, copy or forward this message. Please notify the sender immediately, delete it from your system and destroy any copies. You may not further disclose or distribute this email or its attachments.
