On Mon, Jul 25, 2011 at 6:41 PM, aaron morton aa...@thelastpickle.com wrote:
There are no hard and fast rules to add new nodes, but here are two
guidelines:
1) Single node load is getting too high, rule of thumb is 300GB is probably
too high.
What is that rule of thumb based on? I would
I am using normal SATA disk, actually I was worrying about whether it
is okay if every time cassandra using all the io resources?
further more when is the good time to add more nodes when I was just
using normal SATA disk and with 100r/s it could reach 100 %util
how large the data size it
as the wiki suggested:
http://wiki.apache.org/cassandra/LargeDataSetConsiderations
Adding nodes is a slow process if each node is responsible for a large
amount of data. Plan for this; do not try to throw additional hardware
at a cluster at the last minute.
I really would like to know what's the
There are no hard and fast rules to add new nodes, but here are two guidelines:
1) Single node load is getting too high, rule of thumb is 300GB is probably too
high.
2) There are times when the cluster cannot keep up with throughout, for example
the client is getting TimedOutExceptions or
-Original Message-
From: Jonathan Ellis [mailto:jbel...@gmail.com]
Sent: Saturday, July 23, 2011 5:05 PM
To: user@cassandra.apache.org
Subject: Re: do I need to add more nodes? minor compaction eat all IO
On Sat, Jul 23, 2011 at 4:16 PM, Francois Richard frich...@xobni.com wrote:
My understanding
: Saturday, July 23, 2011 5:05 PM
To: user@cassandra.apache.org
Subject: Re: do I need to add more nodes? minor compaction eat all IO
On Sat, Jul 23, 2011 at 4:16 PM, Francois Richard frich...@xobni.com wrote:
My understanding is that during compaction cassandra does a lot of non
sequential
This really depends on your disks setup.
When you run iostat under high load, do you see a high number of r/s but the
rMB/s is not so great?
I usually use:
iostat -x -m sdb sdc 1 to monitor situation like this.
In my case my disk setup is the following:
OS -- /sda
Cassandra CommitLogs --
On Sat, Jul 23, 2011 at 4:16 PM, Francois Richard frich...@xobni.com wrote:
My understanding is that during compaction cassandra does a lot of non
sequential readsa then dumps the results with a big sequential write.
Compaction reads and writes are both sequential, and 0.8 allows
setting a
