Okay, it looks like we have found the problem.
What had happened was that the infrastructure team had used the same image to
prepare the different nodes. Unfortunately because there was an issue with the
original image, the problem was migrated across to the other node thus breaking
the
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 anthony.ikeda@gmail.com
Date: Tue, August 09,
Tim do you know if this is the actual reason that is causing the broken
pipe? I'm having a hard time convincing my team that modifying this value
will fix the issue.
Jonathan, do you know if there is a valid explanation on why Tim no longer
has the problem based on this change?
Anthony Ikeda
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
It's probably a network thing.
The only thing I can think of in cassandra is thrift_max_message_length_in_mb
in the config. That config setting will result in a TException thrown on the
server side (i think), not sure if that makes the server kill the socket. I
would hope the error returns to
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
On Tue, Aug 2, 2011 at 4:36 PM, Anthony Ikeda
anthony.ikeda@gmail.com 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 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
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
On Tue, Aug 2, 2011 at 6:13 PM, Anthony Ikeda
anthony.ikeda@gmail.com 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
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] -
11 matches
Mail list logo
