And you pass the vclock back after a GET with the next POST? Unless we get a look at the vclocks then it's hard to say why or where you have concurrency. But since concurrency is ultimately unavoidable using riak, why the concern? Can your application/data model handle it is the main question?
On 5 Mar 2016, at 19:04, Qiang Cao <caoqiang...@gmail.com> wrote: > Thanks, Russell! I do a GET immediately after a POST is done. I use apache > httpclient, which handles requests synchronously. On the client, POSTs and > GETs are sent out sequentially. > > On Sat, Mar 5, 2016 at 1:57 PM, Russell Brown <russell.br...@me.com> wrote: > > On 5 Mar 2016, at 18:43, Qiang Cao <caoqiang...@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. > > How does the quorum work here? > > Thanks, > Qiang > _______________________________________________ > 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
