I did some tests and saw that it is correct only for very recent keys. The DB becomes consistent for specific key very fast (few seconds) at least for 5 nodes in 1Gbit network (which seems to be enough or almost enough for required capacity and throughput with bitcask backend).
Pavel On Thu, Oct 18, 2012 at 4:53 PM, Reid Draper <reiddra...@gmail.com> wrote: > > On Oct 18, 2012, at 7:42 AM, Yassen Damyanov <yassen....@gmail.com> wrote: > > > Hi everyone, > > > > Absolutely new (and ignorant) to NoSQL solutions and to Riak (my > > apologies; but extensive experience with SQL RDBMS). > > --snip-- > > > > > The application should be able to write several hundreds of new > > records per second, but first check if the unique key already exists. > > Writing is to be done only if it is not there. If it is, the app needs > > to retrieve the whole record and return it to the client and no > > writing is done in this case. > > Since Riak is an eventually consistent database, you will not be able to > tell > with 100% certainty that a key or does not exist. If this is a _firm > requirement_, > you'll need to either use another db or some external service to provide > this > guarantee. > > Reid > > > > > _______________________________________________ > > riak-users mailing list > > 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 >
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
