Hello all,
I am seeing this exception in 4.1 Cassandra:
ERROR [pool-1-thread-64] 2009-11-02 20:24:32,606 Cassandra.java (line
800) Internal error processing get_key_range
java.lang.RuntimeException: java.util.concurrent.TimeoutException:
Operation timed out.
at
org.apache.cassandra.service.StorageProxy.getKeyRange(StorageProxy.java:513)
at
org.apache.cassandra.service.CassandraServer.get_key_range(CassandraServer.java:598)
at
org.apache.cassandra.service.Cassandra$Processor$get_key_range.process(Cassandra.java:794)
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.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)
Caused by: java.util.concurrent.TimeoutException: Operation timed out.
at org.apache.cassandra.net.AsyncResult.get(AsyncResult.java:97)
at
org.apache.cassandra.service.StorageProxy.getKeyRange(StorageProxy.java:509)
... 7 more
in the cassandra logs. This is probably related to
https://issues.apache.org/jira/browse/CASSANDRA-507 because I have too
many consecutive deletes.
The weird thing is that none of my clients are calling get_key_range
on the cassandra servers, so this exception baffles me. Why would I be
seeing these exceptions then? Does cassandra internally make any calls
to get_key_range?
Thanks
Ray
