Some potential problems:
1) sounds like you are using OPP/BOP and not adjusting tokens to
balance the data on each node
2) 8 client threads is not enough to saturate 16 cassandra cores
3) if your commitlog is not on a separate device from your data
directories you will have a lot of contention bet
Hi
I'll explain a bit. I'm working with Abhinav.
We've an application which was earlier based on Lucene which would
index a huge volume of data, and later use the indices to fetch data
and perform a fuzzy matching operation. We wanted to use Cassandra
primarily because of the sharding/availabilit
Are you using Virtual Machines to run Cassandra? Ive found that performance
in VMs is crap
Nicolas Santini
On Thu, Feb 3, 2011 at 11:17 PM, aaron morton wrote:
> This page has a guide to setting the initial tokens for the nodes
> http://wiki.apache.org/cassandra/Operations#Ring_management
>
> <
This page has a guide to setting the initial tokens for the nodes
http://wiki.apache.org/cassandra/Operations#Ring_management
You can also use the bin/nodetool cfstats command or JConsole to check the
maximum row size in each node, to see if you have a monster row.
Aaron
On 3/02/2011, at 10:22
Hi Peter,
Thanks for your reply.
Our application is multi-threaded. we are using 8 core machine. In our
application we are using 4 column families out of which one column family is
containing rows whose size is huge relative to size of the rows in other
column families.
In the ring the balance i
> First time I tun single instance of Cassandra and my application on a system
> (16GB ram and 8 core), the time taken was 480sec.
> When I added one more system ,(means this time I was running 2 instance
> of Cassandra in cluster) and running application from single client , I
> found time taken i
