Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 79AA04CC3 for ; Fri, 13 May 2011 03:10:30 +0000 (UTC) Received: (qmail 47809 invoked by uid 500); 13 May 2011 03:10:28 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 47250 invoked by uid 500); 13 May 2011 03:10:27 -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 47242 invoked by uid 99); 13 May 2011 03:10:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 May 2011 03:10:27 +0000 X-ASF-Spam-Status: No, hits=3.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of xiaowei609@gmail.com designates 209.85.215.44 as permitted sender) Received: from [209.85.215.44] (HELO mail-ew0-f44.google.com) (209.85.215.44) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 May 2011 03:10:21 +0000 Received: by ewy19 with SMTP id 19so749604ewy.31 for ; Thu, 12 May 2011 20:10:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=+HldhGvL3wrazbDyUwyjLzQ87MN+2GLrTqZwpBzSzHA=; b=W7WKY3pQ1MhtY/SlwZE2UO9ViOB5e3Vt3K+NrctuQR9PMs5rLbYG5PeEJQfJpttQ2T J4jbEq8CkSml8P20KGiQKSYB1WJppkw8KORqtKkKLEVq9Z6eh1J7Lh2FCUsp2G+ypmAv 4MC0wufqWwSPj/x40tql4+/3fZDUYlcq2kk6I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=AdwMDTLBFN/RttiTFChAQkv5P2+2Yn6v9w1HzIUPTsd+sLKAR/+JNQFTKH0V4FLYGV Q3A4misi7xxkTVitlHNM3Xhhs+WACYdL8JEX08kdQwAHfs3HM4ccwUmJXDo+tmayyA7y 5YIyjU080PPrhQEoaOhx7/vOoRajy/UUYWw0M= MIME-Version: 1.0 Received: by 10.213.98.203 with SMTP id r11mr489109ebn.120.1305256198894; Thu, 12 May 2011 20:09:58 -0700 (PDT) Received: by 10.213.10.131 with HTTP; Thu, 12 May 2011 20:09:58 -0700 (PDT) In-Reply-To: References: Date: Thu, 12 May 2011 23:09:58 -0400 Message-ID: Subject: Re: running TPC-C on cassandra clusters From: Xiaowei Wang To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=00504502d22b13757f04a31fa4f2 --00504502d22b13757f04a31fa4f2 Content-Type: text/plain; charset=ISO-8859-1 Thanks! 2011/5/12 Jonathan Ellis > Not if you want the pausing/marking down fixes that were done more > recently. :) > > On Thu, May 12, 2011 at 8:39 PM, Xiaowei Wang > wrote: > > Oh sorry, we use cassandra-0.7.4 already. Is the version fine? > > > > 2011/5/12 Jonathan Ellis > >> > >> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7 > >> > >> On Thu, May 12, 2011 at 8:33 PM, Xiaowei Wang > >> wrote: > >> > Thanks Jonathan, but can you provide some links about 0.7 svn branch? > >> > > >> > 2011/5/12 Jonathan Ellis > >> >> > >> >> I'd recommend trying the 0.7 svn branch (soon to be voted on as > 0.7.6) > >> >> > >> >> On Thu, May 12, 2011 at 3:09 PM, Xiaowei Wang > >> >> wrote: > >> >> > Hi all, > >> >> > > >> >> > My partner and I currently using cassandra cluster to run TPC-C. We > >> >> > first > >> >> > use 2 ec2 nodes to load 20 warehouses. One(client node) has 8 > cores, > >> >> > the > >> >> > other(worker node) has 4 cores. During the loading time, either the > >> >> > client > >> >> > node or the worker node will "down"(cannot be detected) randomly > and > >> >> > then > >> >> > "up" again in a short time. If the two nodes both down, we failed > in > >> >> > loading. If only one of them down, we can continue to load data. > >> >> > > >> >> > The problem is if we use multiple threads(we write multiprocess > >> >> > code), > >> >> > say 4 > >> >> > clients threads, some of them might be stop at the point one of the > >> >> > nodes > >> >> > first down, and the dead threads will never come back.... This will > >> >> > not > >> >> > only > >> >> > enlarge our loading time, but also effect the amount of data we can > >> >> > load. > >> >> > > >> >> > So we need to figure out why the nodes continue to be up and down > and > >> >> > fix > >> >> > this problem. > >> >> > > >> >> > Thanks for any help! > >> >> > > >> >> > Best, > >> >> > Xiaowei > >> >> > > >> >> > > >> >> > >> >> > >> >> > >> >> -- > >> >> Jonathan Ellis > >> >> Project Chair, Apache Cassandra > >> >> co-founder of DataStax, the source for professional Cassandra support > >> >> http://www.datastax.com > >> > > >> > > >> > >> > >> > >> -- > >> Jonathan Ellis > >> Project Chair, Apache Cassandra > >> co-founder of DataStax, the source for professional Cassandra support > >> http://www.datastax.com > > > > > > > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of DataStax, the source for professional Cassandra support > http://www.datastax.com > --00504502d22b13757f04a31fa4f2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thanks!

2011/5/12 Jonathan Ellis <jbellis@gmail.com>= ;
Not if you want the pausing/marking down fixes that were done more recently= . :)

On Thu, May 12, 2011 at 8:39 PM, Xiaowei Wang <xiaowei609@gmail.com> wrote:
> Oh sorry, we use cassandra-0.7.4 already. Is the version fine?
>
> 2011/5/12 Jonathan Ellis <jbel= lis@gmail.com>
>>
>> https://svn.apache.org/repos/asf/cassandra/br= anches/cassandra-0.7
>>
>> On Thu, May 12, 2011 at 8:33 PM, Xiaowei Wang <xiaowei609@gmail.com>
>> wrote:
>> > Thanks Jonathan, but can you provide some links about 0.7 svn= branch?
>> >
>> > 2011/5/12 Jonathan Ellis <jbellis@gmail.com>
>> >>
>> >> I'd recommend trying the 0.7 svn branch (soon to be v= oted on as 0.7.6)
>> >>
>> >> On Thu, May 12, 2011 at 3:09 PM, Xiaowei Wang <xiaowei609@gmail.com>
>> >> wrote:
>> >> > Hi all,
>> >> >
>> >> > My partner and I currently using cassandra cluster t= o run TPC-C. We
>> >> > first
>> >> > use 2 ec2 nodes to load 20 warehouses. One(client no= de)=A0 has 8 cores,
>> >> > the
>> >> > other(worker node) has 4 cores. During the loading t= ime, either the
>> >> > client
>> >> > node or the worker node will "down"(cannot= be detected) randomly and
>> >> > then
>> >> > "up" again in a short time. If the two nod= es both down, we failed in
>> >> > loading. If only one of them down, we can continue t= o load data.
>> >> >
>> >> > The problem is if we use multiple threads(we write m= ultiprocess
>> >> > code),
>> >> > say 4
>> >> > clients threads, some of them might be stop at the p= oint one of the
>> >> > nodes
>> >> > first down, and the dead threads will never come bac= k.... This will
>> >> > not
>> >> > only
>> >> > enlarge our loading time, but also effect the amount= of data we can
>> >> > load.
>> >> >
>> >> > So we need to figure out why the nodes continue to b= e up and down and
>> >> > fix
>> >> > this problem.
>> >> >
>> >> > Thanks for any help!
>> >> >
>> >> > Best,
>> >> > Xiaowei
>> >> >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Jonathan Ellis
>> >> Project Chair, Apache Cassandra
>> >> co-founder of DataStax, the source for professional Cassa= ndra support
>> >> htt= p://www.datastax.com
>> >
>> >
>>
>>
>>
>> --
>> Jonathan Ellis
>> Project Chair, Apache Cassandra
>> co-founder of DataStax, the source for professional Cassandra supp= ort
>> http://www.d= atastax.com
>
>



--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.c= om

--00504502d22b13757f04a31fa4f2--