You'll need to provide more information, from the TP stats the read stage could not keep up. If the node is not CPU bound then it is probably IO bound.
What sort of read? How many columns was it asking for ? How many columns do the rows have ? Was the test asking for different rows ? How many ops requests per second did it get up to? What do the io stats look like ? What does nodetool cfhistograms say ? Aaron On 12 Apr 2011, at 13:02, mcasandra wrote: > But I don't understand the reason for oveload. It was doing simple read of 12 > threads and reasing 50000 rows. Avg CPU only 20%, No GC issues that I see. I > would expect cassandra to be able to process more with 6 nodes, 12 core, 96 > GB RAM and 4 GB heap. > > -- > View this message in context: > http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Timeout-during-stress-test-tp6262430p6263470.html > Sent from the cassandra-u...@incubator.apache.org mailing list archive at > Nabble.com.
