> [30/07/2013 00:04:50] Read Exception (Thread: 5007; Host: 10.191.54.26): > TimedOutException() it means the cluster is over loaded or suffered a failure while processing a request. A well behaved client should retry the request so long as counters are not being used.
Your request went to a coordinator node, it checked that CL replicas were available for the request before starting it. It then timed out waiting for CL replicas to return. This could be because they failed or because they are over loaded. Cheers ----------------- Aaron Morton Cassandra Consultant New Zealand @aaronmorton http://www.thelastpickle.com On 30/07/2013, at 1:00 PM, Rodrigo Felix <rodrigofelixdealme...@gmail.com> wrote: > Hi, > > I'm running a heavy load with about 3200 clients accessing cassandra to > execute read and update queries via YCSB. > At certain moment, YCSB starts throwing exceptions indefinitely like the > following: > > [30/07/2013 00:04:50] Read Exception (Thread: 5007; Host: 10.191.54.26): > TimedOutException() > [30/07/2013 00:04:50] Read Exception (Thread: 4840; Host: 10.191.54.26): > TimedOutException() > [30/07/2013 00:04:50] Read Exception (Thread: 5007; Host: 10.139.3.20): > InvalidRequestException(why:You have not set a keyspace for this session) > [30/07/2013 00:04:50] Read Exception (Thread: 1644; Host: 10.191.54.26): > TimedOutException() > > I'm using Cassandra 1.1.5 in a cluster with 2 seeds and 2 other nodes that > I add (remove) on demand. Each node is a m1.large machine on Amazon. > Any suggestion on what it could be? > Unfortunately, upgrading the EC2 instance type is not an option for me. > > Other info: > rpc_timeout_in_ms: 30000 > thrift_framed_transport_size_in_mb: 60 > thrift_max_message_length_in_mb: 64 > > Att. > > Rodrigo Felix de Almeida > LSBD - Universidade Federal do Ceará > Project Manager > MBA, CSM, CSPO, SCJP
