Dear Riak Team,
I and my team used riak as database for my production with an cluster
including 5 nodes.
While production run, we meet an critical bug that is sometimes fail to
update document.
I and my colleagues performed debug and detected an issue with the scenario
as follow:
+ fetch documen
ected the context which allows Riak to resolve conflicts
> was not present in your data, but I see it in your map structure. Thanks
> for supplying such a detailed description.
>
> How fast is your turnaround time between an update and a fetch? Even if
> the cluster is healthy it’s n
staurant_id">>,register},{register,<<>>,<<"
rest848e042b3a0488640981c8a6dc4a8281">>}},{{<<"restaurant_
status_id">>,register},{register,<<>>,<<"inactive">>}}
,{{<<"start_time">>,register},{reg
ot;false">>}},
{update,{<<"id">>,register},
{assign,<<"menufe89488afa948875cab6b0b18d579f21">>}},
{update,{<<"end_time">>,register},{assign,<<"dont_use">>}},{update,{<<"currency">>,register},{assign,<<"cad"
in you’re updating all those registers in one go? Out of interest, what
> happens if you update a single register at a time?
>
> On 7 Feb 2017, at 10:02, my hue wrote:
>
> > Dear Russel,
> >
> > > Can you run riakc_map:to_op(Map). and show me the output of that,
>
Dear Russel,
Let me try with your suggestion with an new, empty key and use modify_type
to update a single register.
And I will feedback to you on my result test.
Best regards,
Hue Tran
On Tue, Feb 7, 2017 at 5:37 PM, Russell Brown wrote:
>
> On 7 Feb 2017, at 10:27, my hue
;dvv_enabled":true*
,"dw":"quorum",*"last_write_wins":false*
,"linkfun":{"mod":"riak_kv_wm_link_walker","fun":"mapreduce_linkfun"},
*"n_val":3*,"name":"*bucket-name*
","notfound_o
