Re: timeout error for size>40k & changing q_limit has no affect

Hi Venki, I know this email is about two months late, but I figured it was worth responding to as I've had this response as a draft for the last 60 or days or so. :) At any rate, it *looks* like you are (or were) hitting this: https://github.com/basho/riak_kv/issues/290 It has been patched and

Re: More Migration Questions

G'day Tom and Matt. Thanks for your suggestions. Even though our two cluster networks are separate it would theoretically be possible to have nodes from the new cluster join the old cluster and migrate data that way. However, we would prefer to leave the old cluster untouched as much as possib

Re: More Migration Questions

I still haven't really gotten to the bottom of the best way to do this (short of paying for MDC

Re: More Migration Questions

Hi Tom I'd be very interested to know if Shane's approach should work, or if you know of any good reason why that approach would cause issues. Also, aren't there several very real business use cases here that users of Riak will inevitably encounter, and must be able to satisfy? Shane mentions two

Re: ANN: riak-js 0.9.0 released

+1 Thanks. I've been waiting for this for a long time. Already using the older version and will migrate to this one soon. gibraltar. On Nov 13, 2012, at 3:40 PM, Alexander Sicular wrote: > Thanks. Great work. Will definitely check this out. > > @siculars > http://siculars.posterous.com > >

Re: ANN: riak-js 0.9.0 released

Thanks. Great work. Will definitely check this out. @siculars http://siculars.posterous.com Sent from my rotary phone. On Nov 13, 2012 3:30 PM, "Mathias Meyer" wrote: > I mistyped that indeed. The correct name is indeed riak-js on npmjs. > Sorry! > > Cheers, Mathias > > On Tuesday, 13. Novembe

Re: ANN: riak_dt Preview AMI

AWESOME! thanks for sharing! On 13.11.2012, at 20:33, Jordan West wrote: > Hey Riak Users, > > ami-46a3272f contains a preview release of riak_dt > (http://github.com/basho/riak_dt), which brings support for PN-Counters (and > other future work on CRDTs) to Riak. If you hadn't had a chance to

Re: ANN: riak-js 0.9.0 released

I mistyped that indeed. The correct name is indeed riak-js on npmjs. Sorry! Cheers, Mathias On Tuesday, 13. November 2012 at 21:26, Christopher Meiklejohn wrote: > On Tuesday, November 13, 2012 at 3:24 PM, Alexander Sicular wrote: > > Are you published in npm? > > > > npm install riak is fo

Re: ANN: riak-js 0.9.0 released

On Tuesday, November 13, 2012 at 3:24 PM, Alexander Sicular wrote: > Are you published in npm? > > npm install riak is for the mranney version. It appears you mistyped the library name: https://npmjs.org/package/riak-js npm install riak-js - Chris

Re: ANN: riak-js 0.9.0 released

Are you published in npm? npm install riak is for the mranney version. @siculars http://siculars.posterous.com Sent from my iRotaryPhone On Nov 13, 2012, at 2:33 PM, Mathias Meyer wrote: > Hey all, > > I'm happy to announce the 0.9.0 release of riak-js, the Riak client for > Node.js. It'

ANN: riak-js 0.9.0 released

Hey all, I'm happy to announce the 0.9.0 release of riak-js, the Riak client for Node.js. It's a complete rewrite in plain old JavaScript, bringing some new functionality along the way. You can read all about the fresh release over on the Basho blog [1]. riak-js now has a new home [2] and full

ANN: riak_dt Preview AMI

Hey Riak Users, ami-46a3272f contains a preview release of riak_dt ( http://github.com/basho/riak_dt), which brings support for PN-Counters (and other future work on CRDTs) to Riak. If you hadn't had a chance to check it out I highly suggest watching Russell Brown and Sean Cribbs speak about the w

Re: More Migration Questions

Hi Shane, I'm sorry for the delay on this. Over the weekend I was working to replicate your setup so I can answer your question from experience. Alas, time got the best of me and I have not yet finished. That said, I'm inclined to suggest upgrading riak on your current cluster first and then usin

Re: More Migration Questions

Anyone? Beuller? :-) Installing Riak 1.1.1 on the new nodes, copying the data directories from the old nodes, issuing a "reip" on all the new nodes, starting up, waiting for partition handoffs to complete, shutting down, upgrading to 1.2.1 and starting up again got us to where we want to be. B

Re: Quick Q re: error

I'd guess it's just simple riak.yml support, albeit with an ability to define multiple nodes for the client. We'd also have to add support for Rails: riak.yml would be in one location for Rails apps and another for Ruby apps. On Nov 13, 2012, at 10:40 AM, Sean Cribbs wrote: > Glad you figure

Re: Ruby Riak client -- threadsafe?

Great. Thanks Sean. On 13 November 2012 10:37, Sean Cribbs wrote: > Scott, > > It is generally safe to use the Ruby client from multiple threads. A > few items that are infrequently touched (memoized buckets and their > properties) are not, but normal requests are all handled by a > thread-safe

Re: Quick Q re: error

Glad you figured it out, Martin. As you may have noticed, while Ripple provides the tight Rails integration with initializers and such, the basic client does not. If people think that's a valuable feature, I'd be happy to accept pull-requests. :D On Tue, Nov 13, 2012 at 9:30 AM, Martin Streicher

Re: Key removal using Bitcask and expiry_secs

Hi again Scott, Expired keys in bitcask will be removed from disk when compaction/merging occurs, but until then will exist in the keydir (AFAIK). Reads to an expired key simply return 'not found'. On Mon, Nov 12, 2012 at 5:02 PM, Scott Hyndman wrote: > Hi there, > > When expired, at what point

Re: Ruby Riak client -- threadsafe?

Scott, It is generally safe to use the Ruby client from multiple threads. A few items that are infrequently touched (memoized buckets and their properties) are not, but normal requests are all handled by a thread-safe connection pool. Ripple historically kept a client in the thread-locals in order

Re: Quick Q re: error

The issue was inconsistent configuration. There was a call to Riak::Client.new in config/initializers/riak.rb and two more calls in a method to do searches. I expected Riak::Client.new to perhaps pick up settings from a YML file each time, but I think I was wrong. I changed the code to create o

Re: N val nad W - can write ever fail??

You can use pr and pw to require reads and writes to hit primary vnodes. I suspect this makes it possible to fail writes in the way you are describing. --- Jeremiah Peschka Founder, Brent Ozar Unlimited On Nov 13, 2012, at 12:51 AM, kamiseq wrote: > yes, that was my conclusion thats why my que

Re: N val nad W - can write ever fail??

yes, that was my conclusion thats why my question was 'it is possible to fail write'. in a simple scenario you can use R val to ensure that you have enough nodes to read from and riak will fail if you have less and this could be nice sometimes. my point was that you cannot fail write, riak will nev