cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brandon Williams <dri...@gmail.com>
Subject Re: cassandra instability
Date Sun, 18 Apr 2010 23:51:36 GMT
On Fri, Apr 16, 2010 at 12:50 PM, Lee Parker <lee@socialagency.com> wrote:

> This process is running on two clients each working on a separate part of
> the mysql data which totals to about 70G.  Each time I start it up, it will
> work fine for about 1 hour and then it will crash the servers.  The error
> message on the servers is usually an out of memory error.  I will get
> several time out errors on the clients and occasionally get an error telling
> me that i was missing the timestamp.  The timestamp error is accompanied by
> a server crashing if I use framed transport instead of buffered.  I wasn't
> having the out of memory errors with 0.5.0, but had lots of timeouts and
> some "unknown result" errors.  So we upgraded to 0.6.0 when it became the
> stable release.
>

Did you regenerate the php thrift bindings between 0.5 and 0.6?  There's a
decent chance that thrift made some kind of backwards incompatible change
between those revisions (look in the lib dir of each cassandra version to
determine the thrift svn revision you need.)  If that happened, then it's
possible the old bindings are sending something the newer version does not
understand, and causing you to run into THRIFT-601, crashing the server.

-Brandon

Mime
View raw message