On Jul 9, 2010, at 1:16 PM, maneela a wrote:
> Is there any way to mark cassandra node to keep it as just for replication
> purpose and not to be as Primary for any data range in the ring?
I believe there is. This is what we're doing, but we do all of our writes via a
queue. Derek or Mike fro
ConsistencyLevel.ONE is default option given inside stress.py so I am using
default one
--- On Fri, 7/9/10, Bill de hÓra wrote:
From: Bill de hÓra
Subject: Re: RackAwareStrategy vs RackUnAwareStrategy on AWS EC2 cloud
To: user@cassandra.apache.org
Date: Friday, July 9, 2010, 2:12 PM
east
e and not to be as Primary for any data range in the ring?
Niru
--- On Fri, 7/9/10, Joe Stump wrote:
From: Joe Stump
Subject: Re: RackAwareStrategy vs RackUnAwareStrategy on AWS EC2 cloud
To: user@cassandra.apache.org
Date: Friday, July 9, 2010, 1:41 PM
We had similar issues when we started ru
east: A B C
west: D
Perhaps you are blocking on a write to D - what's your quorum/rf set up
as?
Bill
On Fri, 2010-07-09 at 10:36 -0700, maneela a wrote:
> Are there any known performance issues if cassandra cluster
> launched with RackAwareStrategy because I see huge perfo
We had similar issues when we started running Cassandra on EC2 between multiple
AZ's (not regions; we're working up to that shortly). We ended up building a
rack aware strategy specific to AWS, which is posted somewhere in JIRA.
Basically it uses the AWS API to ensure that replicants are stored
Hi,
Can you post the stress test code and storage.conf used?
I have a cluster in EC2 using RackAware. However, I am in 1 region
(us-east-1) but 2 Availability Zones. Amazon helps to ensure that AZ's are
isolated from each other creating a fail-resistant cluster. But, staying in
the same region
Are there any known performance issues if cassandra cluster launched with
RackAwareStrategy because I see huge performance difference between
RackAwareStrategy vs RackUnAwareStrategy. Here are details:
we have a cluster setup with 4 EC2 X large nodes, 3 of them are running in East
region an
