Hi Jonathan thanks for the reply, I will update the code to 0.4.1 and will check all the logs on all the machines. Just a simple question, when you do a get_key_range and you specify "" and "" for start and end, and the limit is 25, if there are too many entries, does it do a scan to find out the start or is it smart enough to know what the start key is?
On Mon, Oct 19, 2009 at 4:42 PM, Jonathan Ellis <[email protected]> wrote: > You should check the other nodes for potential exceptions keeping them > from replying. > > Without seeing that it's hard to say if this is caused by an old bug, > but you should definitely upgrade to 0.4.1 either way :) > > On Mon, Oct 19, 2009 at 5:51 PM, Ramzi Rabah <[email protected]> wrote: >> Hello all, >> >> I am running into problems with get_key_range. I have >> OrderPreservingPartitioner defined in storage-conf.xml and I am using >> a columnfamily that looks like >> <ColumnFamily CompareWith="BytesType" >> Name="DatastoreDeletionSchedule" >> /> >> >> My command is client.get_key_range("Keyspace1", "DatastoreDeletionSchedule", >> "", "", 25, ConsistencyLevel.ONE); >> >> It usually works fine but after a day or so from server writes into >> this column family, I started getting >> ERROR [pool-1-thread-36] 2009-10-19 17:24:28,223 Cassandra.java (line >> 770) 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:560) >> at >> org.apache.cassandra.service.CassandraServer.get_key_range(CassandraServer.java:595) >> at >> org.apache.cassandra.service.Cassandra$Processor$get_key_range.process(Cassandra.java:766) >> at >> org.apache.cassandra.service.Cassandra$Processor.process(Cassandra.java:609) >> at >> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:253) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) >> at java.lang.Thread.run(Thread.java:619) >> 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:556) >> ... 7 more >> >> I still get the timeout exceptions even though the servers have been >> idle for 2 days. When I restart the cassandra servers, it seems to >> work fine again. Any ideas what could be wrong? >> >> By the way, I am using version:apache-cassandra-incubating-0.4.0-rc2 >> Not sure if this is fixed in the 0.4.1 version >> >> Thanks >> Ray >> >
