IMHO you are going to have more success breaking up your work load to work with the current settings.
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. Cheers ----------------- Aaron Morton Freelance Cassandra Consultant New Zealand @aaronmorton http://www.thelastpickle.com On 17/05/2013, at 3:09 PM, John R. Frank <j...@mit.edu> 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 else. > > > I figured out the problem here and made this ticket in jira: > > https://issues.apache.org/jira/browse/CASSANDRA-5575 > > > 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
