incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aaron morton <aa...@thelastpickle.com>
Subject Re: Several 'TimedOutException' in stress.py
Date Tue, 08 Mar 2011 20:22:59 GMT
Is this a client side time out or a server side one? What does the error stack look like ?

Also check the server side logs for errors. The thrift API will raise a timeout when less
the CL level of nodes return in rpc_timeout. 

Good luck 
Aaron

On 9/03/2011, at 7:37 AM, ruslan usifov wrote:

> 
> 
> 2011/3/8 A J <s5alye@gmail.com>
> Trying out stress.py on AWS EC2 environment (4 Large instances. Each
> of 2-cores and 7.5GB RAM. All in the same region/zone.)
> 
> python stress.py -o insert  -d
> 10.253.203.224,10.220.203.48,10.220.17.84,10.124.89.81 -l 2 -e ALL -t
> 10 -n 500 -S 1000000 -k
> 
> (I want to try with column size of about 1MB. I am assuming the above
> gives me 10 parallel threads each executing 50 inserts sequentially
> (500/10) ).
> 
> Getting several timeout errors.TimedOutException(). With just 10
> concurrent writes spread across 4 nodes, kind of surprised to get so
> many timeouts. Any suggestions ?
> 
> 
> 
> It may by EC2 disc speed degradation (io speed of EC2 instances doesnt const, also can
vary in greater limits)


Mime
View raw message