Call me maybe blog post

Dear list, What is your take on the conclusions drawn in the following blog post? In our setup, we occasionally suffer lost data through simultaneous writes to the same key - which I mitigate to some extent with locks in the application layer. In fact, the resolution in the application is essenti

Re: Riak 1.3.1 Warning start up message. Install from source.

This is nothing to worry about. The low-level details revolve around HiPE http://www.it.uu.se/research/group/hipe/. Bear uses a compile flag to use HiPE for native code loading. We ship an Erlang with HiPE disabled for reasons that caused instability on several platforms. This clash of Bear try

[ANN] A Little Riak Book

I'm happy to finally launch "A Little Riak Book"[1] to the public. Sure, it's been available on github for a while now, but there was no website. Now it's an Official Thing. It's also totally, unregrettably, free (CC BY-NC-SA 3.0). This is not meant to be an advanced or comprehensive book, just

Riak 1.3.1 Warning start up message. Install from source.

Hi, I built Riak 1.3.1 from source following these instructions: Erlang- http://docs.basho.com/riak/latest/tutorials/installation/Installing-Erlang/#Installing-on-GNU-Linux Riak - http://docs.basho.com/riak/latest/tutorials/installation/Installing-Riak-from-Source/ It seems to run fine, but ther

Riaktor: a Promise-based async API for Riak

I'm stretching the legs on our new async framework Reactor [1] and I created a quite small helper class to enable efficient async operation of the official Java client. I'm calling it Riaktor (even though there's apparently an old Ruby gem of the same name that hasn't been updated in several yea

Re: First Write Wins

After some asking around, I suspect that any activity on the immutability front will have to wait until we've rolled strong consistency capabilities into Riak. Scott Fritchie pointed out something I hadn't considered: even with pw/pr values, it's still possible to end up in an inconsistent state

Re: multi datacenter replication

Absolutely. Let's keep in sync ourselves on that. I'm very curious how the implementation moves forward & will definitely keep you and the team in the loop on Riak features & especially replication features. Cheers! -Adron On Thu, May 16, 2013 at 11:53 AM, Patrick Christopher < pat.christop...@g

Re: Java client and siblings question

If you're going to use the withoutFetch() method it is required that you use that @RiakVClock annotated field in your class - you need to store the vclock from when you fetched in that field. When you call StoreObject.execute() it is extracted from your object and passed to the Converter.fromDomai

Re: Java client and siblings question

Hi Brian, Thanks for the response.  I am not using the default JSONConverter, but have my own. The way I am currently resolving siblings is as follows: Create a new object Merge fields (using whatever logic) Return new object with merged fields In this case, what should I use for the vclock fo

Re: Java client and siblings question

Hello! When you do your fetch (read) and resolve any conflicts, you're going to get a vector clock along with each sibling. If you're using the default JSONConverter it will be stored in your POJO's @RiakVClock annotated field. That's the vector clock you're going to use when you do your store (wr

Re: How to achieve good performance on riak with AWS.

Thanks for the reply. Replying inline. On Sun, May 19, 2013 at 8:35 PM, Christian Dahlqvist wrote: > > Hi Abhishek, > > I have a few suggestions that may be worthwhile testing in order to get > better performance from your cluster: > > 1) Ensure you have followed the guidelines for EC2 instance