*Reply-To: *"user@cassandra.apache.org" <user@cassandra.apache.org>
> *Date: *Monday, December 26, 2016 at 2:02 PM
> *To: *"user@cassandra.apache.org" <user@cassandra.apache.org>
> *Subject: *Re: Has anyone deployed a production cluster with less than
ww.aspect.com/>
[mailSigLogo-rev.jpg]
From: Jonathan Haddad <j...@jonhaddad.com>
Reply-To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Date: Monday, December 26, 2016 at 2:02 PM
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Subject: Re: Has
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
> wrote:
My
There's nothing wrong with running a 3 node DC. A million writes an hour
is averaging less than 300 writes a second, which is pretty trivial.
Are you running provisioned SSD EBS volumes or the traditional, awful ones?
RF=2 with Quorum is kind of pointless, that's the same as CL=ALL. Not
It depends on a lot of factors.
What causes the cluster to get crazy? I/O, Network, CPU?
I manage clusters of all sizes (even 3 nodes per DC) but it all depends on
usage and configuration.
Regards,
Carlos
Regards,
Carlos Juzarte Rolo
Cassandra Consultant / Datastax Certified Architect /
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