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
We’ve collapsed our 2 DC – 3 node Cassandra clusters into a single 6 node
Cassandra cluster split between two AWS availability zones.
Are there any behaviors we need to take into account to ensure the Cassandra
cluster stability with this configuration?
RICHARD NEY
TECHNICAL DIRECTOR, RESEARCH
igitalis.io<http://digitalis.io> | Fully Managed Open
Source Data Technologies
+44(0)20 8123 4053 | joh...@digitalis.io<mailto:joh...@digitalis.io>
On 2 Jan 2017, at 18:59, Ney, Richard
<richard@aspect.com<mailto:richard@aspect.com>> wrote:
Hi Amit,
I’m seeing “no
Johnny
--
Johnny Miller
Co-Founder & CTO @ digitalis.io<http://digitalis.io> | Fully Managed Open
Source Data Technologies
+44(0)20 8123 4053 | joh...@digitalis.io<mailto:joh...@digitalis.io>
On 2 Jan 2017, at 18:59, Ney, Richard
<richard@aspect.com<mailto:richard@a
load is one of the reason for this.
b.)Can you try connecting cqlsh to that node once you get this kind of
msgs. Are you able to connect?
Regards
Amit
From: Ney, Richard [mailto:richard@aspect.com]
Sent: Monday, January 02, 2017 3:30 PM
To: user@cassandra.apache.org
Subject: Trying to fin
My development team has been trying to track down the cause of this Read
timeout (30 seconds or more at times) exception below. We’re running a 2 data
center deployment with 3 nodes in each data center. Our tables are setup with
replication factor = 2 and we have 16G dedicated to the heap with
Everyone, thank you for the responses
Jon, to answer your question we’re using the General Purpose SSD with IOPS of
1500/3000 so based on your definition I guess we’re using the awful ones since
they aren’t provisioned IOPS. We’re also trying G1 garbage collection.
I also just looked at our
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
