Hi,
I had a 2 node cassandra cluster with replication factor 2 and
OrderPreservingPartitioner but we did not provide InitialToken in
the configuration files. One of the node was affected in the recent AWS EBS
outage and had been partitioned from cluster. However, I continued to allowed
all writ
we have a Cassandra set up running with 4 nodes with Reflicationfactor:2 and
OrderPreservingPartitioner as partitioner but we have not provided InitialToken
values.
Could some one suggest me what is best way to balance my cluster because some
of user threads have suggested "do not ever run nodet
: 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
ubed is a better solution for such things.
--Joe
On Jul 9, 2010, at 11:36 AM, maneela a wrote:
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:
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
not going to work
On Thu, Jul 1, 2010 at 12:16 PM, maneela a wrote:
Can someone direct me how to resolve this issue in cassandra 0.6.2 version?
./stress.py -o insert -n 1 -y regular -d
ec2-174-129-65-118.compute-1.amazonaws.com --threads 5 --keep-going
Created keyspaces. Sleep
Can someone direct me how to resolve this issue in cassandra 0.6.2 version?
./stress.py -o insert -n 1 -y regular -d
ec2-174-129-65-118.compute-1.amazonaws.com --threads 5 --keep-going
Created keyspaces. Sleeping 1s for propagation.Traceback (most recent call
last): File "./stress.py", line
I have provided East node's public DNS/ip address at that both end points
( ListenAddress and ThriftAddress) and West instance's public IP address added
as part of Seed for east.
Similarly I used West node's public DNS/IP for ListenAddress and ThriftAddress
and included East node's public IP a
