Thanks Aaron, will seek help from hector team.
On Tue, Apr 10, 2012 at 3:41 AM, aaron morton wrote:
> Caused by: java.net.SocketTimeoutException: Read timed out
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(SocketInputStream.java:1
> Caused by: java.net.SocketTimeoutException: Read timed out
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(SocketInputStream.java:129)
> at
> org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:127)
>
Thanks Aaron! Here is the exception, is that the timeout between nodes? any
parameter I can change to reduce timeout?
me.prettyprint.hector.api.exceptions.HectorTransportException:
org.apache.thrift.transport.TTransportException:
java.net.SocketTimeoutException: Read timed out
at
me.pretty
You need to see if the timeout is from the client to the server, or between the
server nodes.
If it's server side a TimedOutException will be thrown from thrift. Take a look
at the nodetool tpstats on the servers, you will probably see lots of "Pending"
tasks. Basically the cluster is overload