Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 58302 invoked from network); 8 Mar 2011 20:23:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 8 Mar 2011 20:23:37 -0000 Received: (qmail 27024 invoked by uid 500); 8 Mar 2011 20:23:35 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 26981 invoked by uid 500); 8 Mar 2011 20:23:35 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 26973 invoked by uid 99); 8 Mar 2011 20:23:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Mar 2011 20:23:35 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [208.113.200.5] (HELO homiemail-a79.g.dreamhost.com) (208.113.200.5) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Mar 2011 20:23:29 +0000 Received: from homiemail-a79.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a79.g.dreamhost.com (Postfix) with ESMTP id 972007D405F for ; Tue, 8 Mar 2011 12:23:03 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=thelastpickle.com; h=from :mime-version:content-type:subject:date:in-reply-to:to :references:message-id; q=dns; s=thelastpickle.com; b=ZxoROJrZpp /slooOJS5DmrEAf2qYWEsCzqL7MwHVJewXpJl3qvlJkUbvaQnkoebzDAOh0EcIj9 F90Va3KHMhpZR+WSiiXKKn84NRSCOqtwH6pzJISc3ROpBGNidashLXaeVzvU/JO6 aFYJrvLBXT1p2zjNLHoqgfGStWQOZ56ik= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thelastpickle.com; h=from :mime-version:content-type:subject:date:in-reply-to:to :references:message-id; s=thelastpickle.com; bh=8hrgpBfs1EFOeVaB b00l+34Zpo0=; b=B/ZRUR6XkRd32SAgKxHM7x4XA0oblKhD+wJ4RsUKCHKjUW4o gTRYGMExJBcW+h+tj+k/F2wowL3/aSo2AjJPZRKMwnXn9+/EMkRZcVsCY9RwgRCh UF5xk1cblrcr7rbbIzXOG+qQT9AaBBnr/cBIpk2xXBKGNCcnwwnU410UwA8= Received: from [10.0.1.159] (121-73-157-230.cable.telstraclear.net [121.73.157.230]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: aaron@thelastpickle.com) by homiemail-a79.g.dreamhost.com (Postfix) with ESMTPSA id D2D1B7D4059 for ; Tue, 8 Mar 2011 12:23:02 -0800 (PST) From: aaron morton Mime-Version: 1.0 (Apple Message framework v1082.1) Content-Type: multipart/alternative; boundary=Apple-Mail-36--813967487 Subject: Re: Several 'TimedOutException' in stress.py Date: Wed, 9 Mar 2011 09:22:59 +1300 In-Reply-To: To: user@cassandra.apache.org References: Message-Id: <368585D5-48EA-4CC2-8BE1-C95F42C90177@thelastpickle.com> X-Mailer: Apple Mail (2.1082.1) --Apple-Mail-36--813967487 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii 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.=20 Good luck=20 Aaron On 9/03/2011, at 7:37 AM, ruslan usifov wrote: >=20 >=20 > 2011/3/8 A J > 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.) >=20 > 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 >=20 > (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) ). >=20 > Getting several timeout errors.TimedOutException(). With just 10 > concurrent writes spread across 4 nodes, kind of surprised to get so > many timeouts. Any suggestions ? >=20 >=20 >=20 > It may by EC2 disc speed degradation (io speed of EC2 instances doesnt = const, also can vary in greater limits) --Apple-Mail-36--813967487 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii 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)

--Apple-Mail-36--813967487--