Les, In Riak, there is no single primary copy considered the canonical version. For each key, there will be N (3 by default) partitions responsible for storing the associated value. In effect, there are N primaries for any key. This is how Riak makes its availability guarantees, as well as why "absolute consistency" is difficult.
-- Ian Plosker <i...@basho.com (mailto:i...@basho.com)> Developer Advocate Basho Technologies, Inc. On Tuesday, January 10, 2012 at 10:09 PM, Les Mikesell wrote: > On Tue, Jan 10, 2012 at 8:52 PM, Justin Sheehy <jus...@basho.com > (mailto:jus...@basho.com)> wrote: > > > > On Jan 10, 2012, at 9:42 PM, Les Mikesell wrote: > > > > > How do things like mongo and elasticsearch manage atomic operations > > > while still being redundant? > > > > > > > > > Most such systems use some variant of primary copy replication, also known > > as master/slave replication. > > > > That approach can provide consistency, but has much weaker availability > > properties. > > Doesn't riak need some kind of partition owner/master concept to > control migration? And if it has that, why can't the client request > that an operation happens on the partition owner/master first for > things that need consistency? > > -- > Les Mikesell > lesmikes...@gmail.com (mailto:lesmikes...@gmail.com) > > _______________________________________________ > riak-users mailing list > riak-users@lists.basho.com (mailto:riak-users@lists.basho.com) > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > >
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
