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.