Return-Path: 
 <cassandra-user-return-949-apmail-incubator-cassandra-user-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-cassandra-user-archive@minotaur.apache.org
Received: (qmail 14150 invoked from network); 19 Oct 2009 23:50:01 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 19 Oct 2009 23:50:01 -0000
Received: (qmail 95102 invoked by uid 500); 19 Oct 2009 23:50:01 -0000
Delivered-To: apmail-incubator-cassandra-user-archive@incubator.apache.org
Received: (qmail 95067 invoked by uid 500); 19 Oct 2009 23:50:01 -0000
Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:cassandra-user-help@incubator.apache.org>
List-Unsubscribe: <mailto:cassandra-user-unsubscribe@incubator.apache.org>
List-Post: <mailto:cassandra-user@incubator.apache.org>
List-Id: <cassandra-user.incubator.apache.org>
Reply-To: cassandra-user@incubator.apache.org
Delivered-To: mailing list cassandra-user@incubator.apache.org
Received: (qmail 95058 invoked by uid 99); 19 Oct 2009 23:50:01 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Oct 2009 23:50:01 +0000
X-ASF-Spam-Status: No, hits=-2.6 required=5.0
	tests=BAYES_00
X-Spam-Check-By: apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Received: from [74.125.149.199] (HELO na3sys009aog108.obsmtp.com)
 (74.125.149.199)
    by apache.org (qpsmtpd/0.29) with SMTP; Mon, 19 Oct 2009 23:49:58 +0000
Received: from source ([209.85.216.198]) by na3sys009aob108.postini.com
 ([74.125.148.12]) with SMTP
	ID DSNKStz7EMPmcmNktR4AvaX1JXx96lNH7BJ7@postini.com;
 Mon, 19 Oct 2009 16:49:38 PDT
Received: by mail-px0-f198.google.com with SMTP id 36so3697242pxi.18
        for <cassandra-user@incubator.apache.org>;
 Mon, 19 Oct 2009 16:49:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.114.7.39 with SMTP id 39mr7606115wag.188.1255996176475; Mon,
	19 Oct 2009 16:49:36 -0700 (PDT)
In-Reply-To: <e06563880910191642t253a0016n5c99db875ef6a4bb@mail.gmail.com>
References: <a1625f290910191551n41983840s3edc815d38f7009c@mail.gmail.com>
	 <e06563880910191642t253a0016n5c99db875ef6a4bb@mail.gmail.com>
Date: Mon, 19 Oct 2009 16:49:36 -0700
Message-ID: <a1625f290910191649v627ec009o19ed01d95a62b463@mail.gmail.com>
Subject: Re: Encountering timeout exception when running get_key_range
From: Ramzi Rabah <rrabah@playdom.com>
To: cassandra-user@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

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 <jbellis@gmail.com> 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 <rrabah@playdom.com> 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
>> =A0 =A0 <ColumnFamily CompareWith=3D"BytesType"
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Name=3D"DatastoreDeletionSchedule"
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 />
>>
>> My command is client.get_key_range("Keyspace1", "DatastoreDeletionSchedu=
le",
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0"", "", 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.
>> =A0 =A0 =A0 =A0at org.apache.cassandra.service.StorageProxy.getKeyRange(=
StorageProxy.java:560)
>> =A0 =A0 =A0 =A0at org.apache.cassandra.service.CassandraServer.get_key_r=
ange(CassandraServer.java:595)
>> =A0 =A0 =A0 =A0at org.apache.cassandra.service.Cassandra$Processor$get_k=
ey_range.process(Cassandra.java:766)
>> =A0 =A0 =A0 =A0at org.apache.cassandra.service.Cassandra$Processor.proce=
ss(Cassandra.java:609)
>> =A0 =A0 =A0 =A0at org.apache.thrift.server.TThreadPoolServer$WorkerProce=
ss.run(TThreadPoolServer.java:253)
>> =A0 =A0 =A0 =A0at java.util.concurrent.ThreadPoolExecutor$Worker.runTask=
(ThreadPoolExecutor.java:885)
>> =A0 =A0 =A0 =A0at java.util.concurrent.ThreadPoolExecutor$Worker.run(Thr=
eadPoolExecutor.java:907)
>> =A0 =A0 =A0 =A0at java.lang.Thread.run(Thread.java:619)
>> Caused by: java.util.concurrent.TimeoutException: Operation timed out.
>> =A0 =A0 =A0 =A0at org.apache.cassandra.net.AsyncResult.get(AsyncResult.j=
ava:97)
>> =A0 =A0 =A0 =A0at org.apache.cassandra.service.StorageProxy.getKeyRange(=
StorageProxy.java:556)
>> =A0 =A0 =A0 =A0... 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
>>
>