Re: Trying to find the problem with a broken pipe

2011-08-10 Thread Ikeda Anthony
te: > 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 cassandra. > > Tim > > > Origina

RE: Trying to find the problem with a broken pipe

2011-08-09 Thread Tim Snyder
Anthony, All I can say is that the steps I outlined below fixed my problem and allowed me to process 60 million rows of data. Tim Original Message Subject: Re: Trying to find the problem with a broken pipe From: Anthony Ikeda Date: Tue, August 09, 2011 3:11 am To: user

Re: Trying to find the problem with a broken pipe

2011-08-08 Thread Anthony Ikeda
assandra. > > Tim > > > Original Message ---- > Subject: Re: Trying to find the problem with a broken pipe > From: aaron morton > Date: Fri, August 05, 2011 12:58 am > To: user@cassandra.apache.org > > It's probably a network t

RE: Trying to find the problem with a broken pipe

2011-08-04 Thread Tim Snyder
ondering if it is possibly a > column size streaming issue through the thrift api? I am using Cassandra > 0.8.0 and Hector 0.8.0-1 > > Tim > > Original Message -------- > Subject: Re: Trying to find the problem with a broken pipe > From: Anthony Ikeda > Da

Re: Trying to find the problem with a broken pipe

2011-08-04 Thread aaron morton
.8.0 and Hector 0.8.0-1 > > Tim > > Original Message -------- > Subject: Re: Trying to find the problem with a broken pipe > From: Anthony Ikeda > Date: Tue, August 02, 2011 10:43 pm > To: user@cassandra.apache.org > >> Very

RE: Trying to find the problem with a broken pipe

2011-08-04 Thread Tim Snyder
streaming issue through the thrift api? I am using Cassandra 0.8.0 and Hector 0.8.0-1 Tim Original Message Subject: Re: Trying to find the problem with a broken pipe From: Anthony Ikeda Date: Tue, August 02, 2011 10:43 pm To: user@cassandra.apache.org > Very interesting. Af

Re: Trying to find the problem with a broken pipe

2011-08-02 Thread Anthony Ikeda
> Very interesting. After the second host goes down do you see > "me.prettyprint.hector.api.exceptions.HectorException: All host pools > marked down. Retry burden pushed out to client"? No, the last message is: 2011-08-02 08:43:06,561 INFO [me.prettyprint.cassandra.connection.HConnectionManager]

Re: Trying to find the problem with a broken pipe

2011-08-02 Thread Jim Ancona
On Tue, Aug 2, 2011 at 6:13 PM, Anthony Ikeda wrote: > The link (which I may be misreading) > is http://groups.google.com/group/hector-users/browse_thread/thread/8d7004b6f85a0f2e I hadn't found that one, but I doubt that our issue is related to that. > It's only started happening today and happe

Re: Trying to find the problem with a broken pipe

2011-08-02 Thread Anthony Ikeda
I was thinking, it's only the one function that it has happened to so far with the other functions unaffected. My understanding is that the hector client pool should be shared across functions meaning that other functions should also be affected but they are not. Here is the connection configurati

Re: Trying to find the problem with a broken pipe

2011-08-02 Thread Anthony Ikeda
The link (which I may be misreading) is http://groups.google.com/group/hector-users/browse_thread/thread/8d7004b6f85a0f2e It's only started happening today and happened on 2 occassions (8:43 and 10:21) performing the same function (querying a column family). It seems to be trying to access a conn

Re: Trying to find the problem with a broken pipe

2011-08-02 Thread Jim Ancona
On Tue, Aug 2, 2011 at 4:36 PM, Anthony Ikeda wrote: > I'm not sure if this is a problem with Hector or with Cassandra. > We seem to be seeing broken pipe issues with our connections on the client > side (Exception below). A bit of googling finds possibly a problem with the > amount of data we are

Trying to find the problem with a broken pipe

2011-08-02 Thread Anthony Ikeda
I'm not sure if this is a problem with Hector or with Cassandra. We seem to be seeing broken pipe issues with our connections on the client side (Exception below). A bit of googling finds possibly a problem with the amount of data we are trying to store, although I'm certain our datasets are not a