Do you consider forcing siblings a good idea? I would like to get some input on possible use cases and pitfalls. For instance i have considered to force siblings and then merge them on read instead of fetching an object every time i want to update it (especially with larger objects).
It's not clear from the docs if there are any limitations, will the maximum object size be the limitation:? A section of the docs[1] comees comes to mind: "Having an enormous object in your node can cause reads of that object to crash the entire node. Other issues are increased cluster latency as the object is replicated and out of memory errors." [1] http://docs.basho.com/riak/latest/theory/concepts/Vector-Clocks/#Siblings 2013/11/9 Brian Roach <[email protected]> > On Fri, Nov 8, 2013 at 11:38 AM, Russell Brown <[email protected]> > wrote: > > > If you’re using a well behaved client like the Riak-Java-Client, or any > other that gets a vclock before doing a put, use whatever option stops that. > > for (int i = 0; i < numReplicasWanted; i++) { > bucket.store("key", "value").withoutFetch().execute(); > } > > :) > > - Roach > > _______________________________________________ > riak-users mailing list > [email protected] > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
