I use
<RpcTimeoutInMillis>30000</RpcTimeoutInMillis>
in storage-conf.xml, and for the most part that makes the timeouts go away. My
application would rather wait 30 seconds if needed, since it would otherwise
retry. YMMV. I hear that Cassandra 0.5 will be better at avoiding the
timeouts.
Tim Freeman
Email: tim.free...@hp.com<mailto:tim.free...@hp.com>
Desk in Palo Alto: (650) 857-2581
Home: (408) 774-1298
Cell: (408) 348-7536 (No reception business hours Monday, Tuesday, and
Thursday; call my desk instead.)
From: mobiledream...@gmail.com [mailto:mobiledream...@gmail.com]
Sent: Monday, November 23, 2009 12:26 PM
To: cassandra-user@incubator.apache.org
Subject: Re: java.util.concurrent.TimeoutException: Operation timed out -
received only 0 responses from .
this error keeps coming up...
any ideas on how to avoid this error?
On Wed, Nov 18, 2009 at 11:25 PM,
<mobiledream...@gmail.com<mailto:mobiledream...@gmail.com>> wrote:
Can you plase tell what this error is ?
ERROR - error writing key ruske
java.util.concurrent.TimeoutException: Operation timed out - received only 0
responses from .
at
org.apache.cassandra.service.QuorumResponseHandler.get(QuorumResponseHandler.java:88)
at
org.apache.cassandra.service.StorageProxy.insertBlocking(StorageProxy.java:164)
at
org.apache.cassandra.service.CassandraServer.doInsert(CassandraServer.java:468)
at
org.apache.cassandra.service.CassandraServer.batch_insert(CassandraServer.java:448)
at
org.apache.cassandra.service.Cassandra$Processor$batch_insert.process(Cassandra.java:854)
at
org.apache.cassandra.service.Cassandra$Processor.process(Cassandra.java:627)
at
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:253)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Errors
--
Bidegg worlds best auction site
http://bidegg.com
