Jun -- this is a great catch. Do you know if this problem is reproducible with smaller column values? 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 <[email protected]> wrote: > 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 > > [email protected] > > > [image: Inactive hide details for Jonathan Ellis <[email protected]>]Jonathan > Ellis <[email protected]> > > > > *Jonathan Ellis <[email protected]>* > > 06/22/2009 08:14 AM > Please respond to > [email protected] > > > To > > [email protected] > cc > > > Subject > > VOTE: Cassandra 0.3.0 release > > 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<http://people.apache.org/%7Ejbellis/cassandra/cassandra-0.3.0-rc2.tar.gz> > > Voting will run for 3 days. > > +1 from me. > > -Jonathan > >
