Return-Path: Delivered-To: apmail-incubator-cassandra-dev-archive@minotaur.apache.org Received: (qmail 30272 invoked from network); 23 Jun 2009 16:35:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 23 Jun 2009 16:35:01 -0000 Received: (qmail 97697 invoked by uid 500); 23 Jun 2009 16:35:12 -0000 Delivered-To: apmail-incubator-cassandra-dev-archive@incubator.apache.org Received: (qmail 97675 invoked by uid 500); 23 Jun 2009 16:35:11 -0000 Mailing-List: contact cassandra-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cassandra-dev@incubator.apache.org Delivered-To: mailing list cassandra-dev@incubator.apache.org Received: (qmail 97665 invoked by uid 99); 23 Jun 2009 16:35:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Jun 2009 16:35:11 +0000 X-ASF-Spam-Status: No, hits=-0.6 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,TVD_FW_GRAPHIC_NAME_MID X-Spam-Check-By: apache.org Received-SPF: unknown (nike.apache.org: error in processing during lookup of junrao@almaden.ibm.com) Received: from [32.97.182.145] (HELO e5.ny.us.ibm.com) (32.97.182.145) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Jun 2009 16:34:59 +0000 Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by e5.ny.us.ibm.com (8.13.1/8.13.1) with ESMTP id n5NGSHpg027939 for ; Tue, 23 Jun 2009 12:28:17 -0400 Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v9.2) with ESMTP id n5NGYccd251014 for ; Tue, 23 Jun 2009 12:34:38 -0400 Received: from d01av04.pok.ibm.com (loopback [127.0.0.1]) by d01av04.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id n5NGYbsc004069 for ; Tue, 23 Jun 2009 12:34:38 -0400 Received: from d01ml604.pok.ibm.com (d01ml604.pok.ibm.com [9.56.227.90]) by d01av04.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id n5NGYbMZ004066 for ; Tue, 23 Jun 2009 12:34:37 -0400 In-Reply-To: Subject: Re: VOTE: Cassandra 0.3.0 release To: cassandra-dev@incubator.apache.org X-Mailer: Lotus Notes Release 7.0 HF277 June 21, 2006 Message-ID: From: Jun Rao Date: Tue, 23 Jun 2009 09:34:46 -0700 X-MIMETrack: Serialize by Router on D01ML604/01/M/IBM(Release 8.5|December 05, 2008) at 06/23/2009 12:34:37 MIME-Version: 1.0 Content-type: multipart/related; Boundary="0__=07BBFF4DDFC919488f9e8a93df938690918c07BBFF4DDFC91948" X-Virus-Checked: Checked by ClamAV on apache.org --0__=07BBFF4DDFC919488f9e8a93df938690918c07BBFF4DDFC91948 Content-type: multipart/alternative; Boundary="1__=07BBFF4DDFC919488f9e8a93df938690918c07BBFF4DDFC91948" --1__=07BBFF4DDFC919488f9e8a93df938690918c07BBFF4DDFC91948 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: quoted-printable Under heavy load and large column values (10s of Ks), we observed that cassandra TCP channels can get jammed. A new patch is provided to https://issues.apache.org/jira/browse/CASSANDRA-220. I see two options: 1) patch #220 to 0.3.0 and release RC3 2) release RC2 with a release note that describes the above potential problem. What do people feel? Jun IBM Almaden Research Center K55/B1, 650 Harry Road, San Jose, CA 95120-6099 junrao@almaden.ibm.com = Jonathan Ellis = = To cassandra-dev@incubator.apache.o= rg 06/22/2009 08:14 = cc AM = Subj= ect VOTE: Cassandra 0.3.0 release = Please respond to = cassandra-dev@inc = ubator.apache.org = = = = It's been two weeks since the last code change on the 0.3 branch and several days since RC2 release with no new bug reports. I move that we release RC2 as 0.3.0 official. svn tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.3= .0-rc2/ binary build: http://people.apache.org/~jbellis/cassandra/cassandra-0.3.0-rc2.tar.gz Voting will run for 3 days. +1 from me. -Jonathan = --1__=07BBFF4DDFC919488f9e8a93df938690918c07BBFF4DDFC91948 Content-type: text/html; charset=US-ASCII Content-Disposition: inline Content-transfer-encoding: quoted-printable

Under heavy load and large column values (10s of Ks), we observed th= at cassandra TCP channels can get jammed. A new patch is provided to https://i= ssues.apache.org/jira/browse/CASSANDRA-220.

I see two options:
1) patch #220 to 0.3.0 and release RC3
2) release RC2 with a release note that describes the above potential p= roblem.

What do people feel?

Jun
IBM Almaden Research Center
K55/B1, 650 Harry Road, San Jose, CA 95120-6099

junrao@almaden.ibm.com

3D"InactiveJonathan Ellis <jbellis@gmail.c= om>


=
          Jonathan Ellis <jbellis@gmail.com>=

          06/22/2009 08:14 AM
          Please respond to
          cassandra-dev@incubator.apache.org

 =
3D=
To
3D""
cassandra-dev@incubator.apache.org
3D=
cc
3D""
3D=
Subject
3D""
VOTE: Cassandra 0.3.0 release
3D=3D""


It's been two weeks since the last code change on the 0.3 branch and several days since RC2 release with no new bug reports.

I move that we release RC2 as 0.3.0 official.

svn tag: https://svn.apache.org/repos/asf/= incubator/cassandra/tags/cassandra-0.3.0-rc2/

binary build: http://people.apache.org/~jbellis/ca= ssandra/cassandra-0.3.0-rc2.tar.gz

Voting will run for 3 days.

+1 from me.

-Jonathan

= --1__=07BBFF4DDFC919488f9e8a93df938690918c07BBFF4DDFC91948-- --0__=07BBFF4DDFC919488f9e8a93df938690918c07BBFF4DDFC91948--