redundant writers

Dan Reverri dan at basho.com
Tue Feb 15 14:57:16 EST 2011


Riak maintains a single value per key and provides mechanisms (vector
clocks) to detect/resolve conflicting values. In the proposed use case the
multiple copies would overwrite each other and Riak, by default, would
return a single value for a requested key.

Behind the scenes Riak determines the appropriate value per key using vector
clocks. More information about vector clocks is available here:
http://blog.basho.com/2010/01/29/why-vector-clocks-are-easy/
http://blog.basho.com/2010/04/05/why-vector-clocks-are-hard/

Thanks,
Dan

Daniel Reverri
Developer Advocate
Basho Technologies, Inc.
dan at basho.com


On Tue, Feb 15, 2011 at 10:11 AM, Les Mikesell <lesmikesell at gmail.com>wrote:

> Is riak suitable as a very reliable store where you have multiple feeds of
> streaming data that are at least theoretically identical?  That is, can you
> count on writing multiple copies with the same keys at the same time to do
> something reasonable regardless of cluster partitioning?  And is this a
> common usage scenario?
>
> --
>  Les Mikesell
>   lesmikesell at gmail.com
>
> _______________________________________________
> riak-users mailing list
> riak-users at lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.basho.com/pipermail/riak-users_lists.basho.com/attachments/20110215/06a099bd/attachment.html>


More information about the riak-users mailing list