Fwd: read timeouts in cassandra 0.6.5

2010-11-05 Thread Adam Crain
Hi, I have a simple keyspace: org.apache.cassandra.locator.RackUnawareStrategy 1 org.apache.cassandra.locator.EndPointSnitch We're using it as a data historian. Many rows of measurments, measurement history is in the columns by milliseconds since UNIX epoch. The single nod

RE: error using get_range_slice with random partitioner

2010-08-13 Thread Adam Crain
David, This much like the behavior I saw... I thought that I might be doing something wrong, but I haven't had the time to check out other clients iteration implementations. What client are you using? -Adam -Original Message- From: David McIntosh [mailto:da...@radiotime.com] Sent: Thu

RE: error using get_range_slice with random partitioner

2010-08-09 Thread Adam Crain
ginal Message- From: th.hel...@gmail.com on behalf of Thomas Heller Sent: Fri 8/6/2010 7:17 PM To: user@cassandra.apache.org Subject: Re: error using get_range_slice with random partitioner On Sat, Aug 7, 2010 at 1:05 AM, Adam Crain wrote: > I took this approach... reject the first r

RE: error using get_range_slice with random partitioner

2010-08-06 Thread Adam Crain
I took this approach... reject the first result of subsequent get_range_slice requests. If you look back at output I posted (below) you'll notice that not all of the 30 keys [key1...key30] get listed! The iteration dies and can't proceed past key2. 1) 1st batch gets 10 unique keys. 2) 2nd batch

RE: error using get_range_slice with random partitioner

2010-08-06 Thread Adam Crain
t the 0.6 branch: svn checkout http://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.6/ cassandra-0.6 Then run `ant` to build the binaries. On Aug 6, 2010, at 2:57 PM, Adam Crain wrote: > Hi Jeremy, > > So, I fixed my client so it preserves the ordering and I get results

RE: error using get_range_slice with random partitioner

2010-08-06 Thread Adam Crain
e was another duplicate bug with get_range_slice that was recently fixed on cassandra-0.6 branch. It's slated for 0.6.5 which will probably be out sometime this month, based on previous minor releases. https://issues.apache.org/jira/browse/CASSANDRA-1145 On Aug 6, 2010, at 10:29 AM, Adam C

RE: error using get_range_slice with random partitioner

2010-08-06 Thread Adam Crain
} } } $have_more = 1; } # end results loop if ($keyrange->{'start_key'} eq $previous_start_key) { $have_more = 0; } } # end while() loop $transport->cl

RE: error using get_range_slice with random partitioner

2010-08-06 Thread Adam Crain
bject: Re: error using get_range_slice with random partitioner Wild guess here, but are you using start_token/end_token here when you should be using start_key? Looks to me like you are trying end_token = ''. HTH, /thomas On Thursday, August 5, 2010, Adam Crain wrote: > Hi, > >

RE: error using get_range_slice with random partitioner

2010-08-05 Thread Adam Crain
esh install, no existing data? On Thu, Aug 5, 2010 at 12:09 PM, Adam Crain wrote: > I've never changed the partitioner from the default random. Other ideas? > > I can insert and do column queries using a single key but not range on CF. > > -Adam > > -Original Message

RE: error using get_range_slice with random partitioner

2010-08-05 Thread Adam Crain
user@cassandra.apache.org Subject: Re: error using get_range_slice with random partitioner Yes, you should be able to use get_range_slices with RP. This stack trace looks like you changed your partitioner after the node already had data in it. On Thu, Aug 5, 2010 at 10:06 AM, Adam Crain wrote: > Hi, &g

error using get_range_slice with random partitioner

2010-08-05 Thread Adam Crain
Hi, I'm on 0.6.4. Previous tickets in the JIRA in searching the web indicated that iterating over the keys in keyspace is possible, even with the random partitioner. This is mostly desirable in my case for testing purposes only. I get the following error: [junit] Internal error processing get_