To note: I still have the problem in before beta 1.1 custom build that
seems to have the fix. I am going to upgrade to 1.1 beta and check if
problem will go away and will file a bug if problem still exists.
BTW: It would be great for cassandra to exit on any fatal errors, like
assertion problems
Fixed in 1.0.3
https://issues.apache.org/jira/browse/CASSANDRA-3482
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 14/03/2012, at 3:45 PM, David Hawthorne wrote:
> 5 node cluster running 1.0.2, doing about 1300 reads and 1300 writes/sec
5 node cluster running 1.0.2, doing about 1300 reads and 1300 writes/sec into 3
column families in the same keyspace. 2 client machines, doing about the same
amount of reads/writes, but one has an average response time in the 4-40ms
range and the other in the 200-800ms range. Both running iden
