cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aaron morton <>
Subject Re: pycassa failures in large batch cycling
Date Fri, 17 May 2013 18:34:41 GMT
IMHO you are going to have more success breaking up your work load to work with the current

The buffers created by thrift are going to eat up the server side memory. They grow dynamically
but persist for the life of the connection. 

Aaron Morton
Freelance Cassandra Consultant
New Zealand


On 17/05/2013, at 3:09 PM, John R. Frank <> wrote:

> On Tue, 14 May 2013, aaron morton wrote:
>>      After several cycles, pycassa starts getting connection failures.
>> Do you have the error stack ?Are the TimedOutExceptions or socket time outs or something
> I figured out the problem here and made this ticket in jira:
> Summary: the Thrift interfaces to Cassandra are simply not able to load large batches
without putting the client into an infinite retry loop.
> Seems that the only robust solutions involve either features added to Thrift and all
Cassandra clients, or a new interface mechanism.
> jrf

View raw message