Bucket properties not updated

Daniel Iwan iwan.daniel at gmail.com
Thu Oct 10 17:09:28 EDT 2013

There is no coordination between servers so concurrent update of properties
is possible.
That would certainly explain a lot.

In my case though I'm setting allow_mult back to true so eventually that
should win? Or would propagation through ring potentially break that logic
and allow_multi = false could win?
Also could clock drift on the servers be problematic here?
It's good to hear you plan to solve that. I'm assuming it's going to be
some sort of vclock causality applied to properties?


On 10 October 2013 21:06, Jordan West <jwest at basho.com> wrote:

> Hi Daniel,
> You mentioned this was running on three servers simultaneously. Is it
> possible that two of the bucket property updates were truly concurrent? If
> so, an implementation detail of bucket properties: they are last-write-wins
> (and unfortunately the resolution is in milliseconds)*. So its feasible
> that in some cases the allow_mult=false would win.
> Cheers,
> Jordan
> *this is something we plan to address in future releases.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.basho.com/pipermail/riak-users_lists.basho.com/attachments/20131010/6afaee29/attachment.html>

More information about the riak-users mailing list