Continuous HTTP POSTs to Riak

Russell Brown russell.brown at me.com
Sat Mar 5 13:57:53 EST 2016


On 5 Mar 2016, at 18:43, Qiang Cao <caoqiang.cs at gmail.com> wrote:

> Just curious. The POSTs are sent out sequentially and a quorum is set up on Riak. I wonder how would it happen that Riak still considers the POST requests concurrent?
Did you read the result of POST 1 before sending POST 2? If not, and you don’t send the causal context, Riak has to view them as concurrent.

> 
> -Qiang
> 
> On Fri, Mar 4, 2016 at 12:27 PM, Qiang Cao <caoqiang.cs at gmail.com> wrote:
> This worked!  Thank you, Vitaly!
> 
> 
> On Fri, Mar 4, 2016 at 3:18 AM, Vitaly E <13vitamins at gmail.com> wrote:
> Hi Qiang,
> 
> Since you are running with allow_mult=false, make sure the clocks of your Riak nodes are synchronized. If they are out of sync, newer values may get overridden by older ones on read, depending on the node a request hits first. Of course this won't cover 100% of cases because a perfect clock synchronization is just impossible.
> 
> Also, setting notfound_ok to "false" may help if you encounter not founds for keys you are sure have been written.
> 
> Good luck!
> Vitaly
> 
> _______________________________________________
> riak-users mailing list
> riak-users at lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com





More information about the riak-users mailing list