get_indexed_slices_result TimedOutException

[Jason Pell]

Hi,

On pelops side, with the default configuration in spring:

<bean class="org.scale7.cassandra.pelops.Cluster">
<constructor-arg value="localhost"/>
<constructor-arg value="${cassandra.listen-port}"/>
<constructor-arg value="false"/>
</bean>

the timeout is set to -1, I am assuming this means no timeout on the
client side. I have a single cassandra node, so my understanding is
that the rpc timeout of 10s does not apply, as its not contacting any
other nodes (Is this correct assumption?)

I get the following exception sporadically in the logs:

INFO | jvm 1 | 2011/02/02 15:50:27 | TimedOutException()
INFO | jvm 1 | 2011/02/02 15:50:27 | at
org.apache.cassandra.thrift.Cassandra
$get_indexed_slices_result.read(Cassandra.java:13315)
INFO | jvm 1 | 2011/02/02 15:50:27 | at
org.apache.cassandra.thrift.Cassandra
$Client.recv_get_indexed_slices(Cassandra.java:780)
INFO | jvm 1 | 2011/02/02 15:50:27 | at
org.apache.cassandra.thrift.Cassandra
$Client.get_indexed_slices(Cassandra.java:752)
INFO | jvm 1 | 2011/02/02 15:50:27 | at
org.scale7.cassandra.pelops.Selector$15.execute(Selector.java:1213)
INFO | jvm 1 | 2011/02/02 15:50:27 | at
org.scale7.cassandra.pelops.Selector$15.execute(Selector.java:1210)
INFO | jvm 1 | 2011/02/02 15:50:27 | at
org.scale7.cassandra.pelops.Operand.tryOperation(Operand.java:56)
INFO | jvm 1 | 2011/02/02 15:50:27 | at
org.scale7.cassandra.pelops.Selector.getIndexedColumns(Selector.java:
1225)
INFO | jvm 1 | 2011/02/02 15:50:27 | at
org.scale7.cassandra.pelops.Selector.getIndexedColumns(Selector.java:
1194)

I am running scale7-pelops-0.911-0.7.0-20101222.025608-3 on a 0.7.0
cassandra on Centos 5.5

[Dan Washusen]

Hi Jason,

It's hard to determine based on the stack trace but it looks like you're seeing Cassandra TimedOutException [1].  The org.scale7.cassandra.pelops.IConnection.Config#timeout property relates the the underlying thrift connection and would throw a TransportException (wrapping a TTransportException)...

Does that clear things up?

Cheers,

Dan

1. TimedOutException - The node responsible for the write or read did not respond during the rpc interval specified in your configuration (default 10s). This can happen if the request is too large, the node is oversaturated with requests, or the node is down but the failure detector has not yet realized it (usually this takes < 30s).

[Jason Pell]

It does - the timeout is not on Pelops end so I need to look at
Cassandra end. That's what I suspected and wanted to confirm

Cheers
Jason

On Wednesday, February 2, 2011, Dan Washusen <d...@reactive.org> wrote:
> Hi Jason,It's hard to determine based on the stack trace but it looks like you're seeing Cassandra TimedOutException [1].  The org.scale7.cassandra.pelops.IConnection.Config#timeout property relates the the underlying thrift connection and would throw a TransportException (wrapping a TTransportException)...

>
> Does that clear things up?

> Cheers,DanTimedOutException - The node responsible for the write or read did not respond during the rpc interval specified in your configuration (default 10s). This can happen if the request is too large, the node is oversaturated with requests, or the node is down but the failure detector has not yet realized it (usually this takes < 30s).