Mailing-List: contact cassandra-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Received-SPF: unknown (nike.apache.org: error in processing during lookup of
 junrao@almaden.ibm.com)
In-Reply-To: <a073486d0906231007l7f3e2101i9485b58a403245ee@mail.gmail.com>
Subject: Re: VOTE: Cassandra 0.3.0 release
To: cassandra-dev@incubator.apache.org
Message-ID: 
 <OF3573A342.1B05A71F-ON882575DE.00601DE5-882575DE.00606E7A@us.ibm.com>
From: Jun Rao <junrao@almaden.ibm.com>
Date: Tue, 23 Jun 2009 10:33:25 -0700
MIME-Version: 1.0
Content-type: multipart/alternative;
	Boundary="0__=07BBFF4DDFF39B758f9e8a93df938690918c07BBFF4DDFF39B75"
Content-Disposition: inline

--0__=07BBFF4DDFF39B758f9e8a93df938690918c07BBFF4DDFF39B75
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: quoted-printable


This problem only shows up when both the writer and the reader try to
update the same socket channel. A writer only needs to update the chann=
el
if it can't write the whole message in one write call. So, if one only
updates and reads a small column at a time, this problem may not show u=
p.

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

junrao@almaden.ibm.com


Sandeep Tata <sandeep.tata@gmail.com> wrote on 06/23/2009 10:07:13 AM:

> Jun -- this is a great catch.
> Do you know if this problem is reproducible with smaller column value=
s?
From
> your example, it looks like it might.
>
> If it *isn't* I'd be comfortable going ahead with RC2 as the 0.3.0
release
> and rolling this and other bugfixes into 0.3.1.
>
>
> On Tue, Jun 23, 2009 at 9:34 AM, Jun Rao <junrao@almaden.ibm.com> wro=
te:
>
> > Under heavy load and large column values (10s of Ks), we observed t=
hat
> > 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 potenti=
al
> > problem.
> >
> > What do people feel?
> >
> > Jun
> > IBM Almaden Research Center
> > K55/B1, 650 Harry Road, San Jose, CA 95120-6099
> >
> > junrao@almaden.ibm.com
> >
> >
> > [image: Inactive hide details for Jonathan Ellis <jbellis@gmail.
> com>]Jonathan
> > Ellis <jbellis@gmail.com>
> >
> >
> >
> >     *Jonathan Ellis <jbellis@gmail.com>*
> >
> >             06/22/2009 08:14 AM
> >             Please respond to
> >             cassandra-dev@incubator.apache.org
> >
> >
> > To
> >
> > cassandra-dev@incubator.apache.org
> > cc
> >
> >
> > Subject
> >
> > VOTE: Cassandra 0.3.0 release
> >
> > It's been two weeks since the last code change on the 0.3 branch an=
d
> > 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<
> http://people.apache.org/%7Ejbellis/cassandra/cassandra-0.3.0-rc2.tar=
.gz>
> >
> > Voting will run for 3 days.
> >
> > +1 from me.
> >
> > -Jonathan
> >
> >=

--0__=07BBFF4DDFF39B758f9e8a93df938690918c07BBFF4DDFF39B75--