I notice you have pending hinted handoffs? Look for errors related to that. We have seen occasional corruptions in the hinted handoff sstables,
If you are stressing the system to its limits, you may also consider playing with more with the number of read/write threads (concurrent_reads/writes) as well as rate limiting the number of requests you can get per node (throttle limit). We have seen similar issue when sending large number of requests to a cluster (read/write threads running out, timeouts, nodes marked as down). Terje We have seen similar issues when On Tue, Apr 12, 2011 at 9:56 AM, aaron morton <aa...@thelastpickle.com>wrote: > It means the cluster is currently overloaded and unable to complete > requests in time at the CL specified. > > Aaron > > On 12 Apr 2011, at 11:18, mcasandra wrote: > > > It looks like hector did retry on all the nodes and failed. Does this > then > > mean cassandra is down for clients in this scenario? That would be bad. > > > > -- > > View this message in context: > http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Timeout-during-stress-test-tp6262430p6263270.html > > Sent from the cassandra-u...@incubator.apache.org mailing list archive > at Nabble.com. > >
