I am getting the same problem (Broken Pipe) on a loader program, after
about 8 million read, write pairs. I am pushing serialized objects into
a column with the program, the object it seems to be doing it on is much
larger than the prior objects, so I am wondering if it is possibly a
column size st
wn on the server side (i think), not sure if
that makes the server kill the socket. I would hope the error returns to
the client.
Perhaps check the server log.
Cheers
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 4 Aug 2011, at 23:05
hange?
Anthony Ikeda
On Thu, Aug 4, 2011 at 11:13 PM, Tim Snyder
wrote:
I no longer get the error on the loader program. The steps I took to
fix
it are increasing the thrift_max_message_length_in_mb msg length,
stopping cassandra, blowing away the prior data store, and then
restarting cass
