yuanbiao
/
emqx
1
0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix(route-sync): ensure batch sync preserve idemopotency

This commit is contained in:
Andrew Mayorov 2024-01-11 19:02:17 +01:00
parent e21a3497c7
commit 2f98f1faaf
No known key found for this signature in database
GPG Key ID: 2837C62ACFBFED5D
1 changed files with 12 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
apps/emqx/src/emqx_router_syncer.erl
View File

@ -312,23 +312,21 @@ stash_add(Prio, ?OP(Action, Topic, Dest, Ctx), Stash) ->
undefined ->
Stash#{Route => {Action, Prio, Ctx}};
RouteOp ->
case merge_route_op(RouteOp, ?ROUTEOP(Action, Prio, Ctx)) of
undefined ->
maps:remove(Route, Stash);
RouteOpMerged ->
RouteOpMerged = merge_route_op(RouteOp, ?ROUTEOP(Action, Prio, Ctx)),
Stash#{Route := RouteOpMerged}
end
end.
merge_route_op(?ROUTEOP(Action, _Prio1, Ctx1), DestOp = ?ROUTEOP(Action)) ->
%% NOTE: This should not happen anyway.
_ = replyctx_send(ignored, Ctx1),
DestOp;
merge_route_op(?ROUTEOP(_Action1, _Prio1, Ctx1), ?ROUTEOP(_Action2, _Prio2, Ctx2)) ->
%% NOTE: Operations cancel each other.
merge_route_op(?ROUTEOP(_Action1, _Prio1, Ctx1), DestOp = ?ROUTEOP(_Action2, _Prio2, _Ctx2)) ->
%% NOTE: Latter cancel the former.
%% Strictly speaking, in ideal conditions we could just cancel both, because they
%% essentially do not change the global state. However, we decided to stay on the
%% safe side and cancel only the former, making batch syncs idempotent.
_ = replyctx_send(ok, Ctx1),
_ = replyctx_send(ok, Ctx2),
undefined.
DestOp.
%%
@ -398,13 +396,13 @@ batch_test() ->
[
{2, ignored},
{1, ok},
{4, ok},
{5, ok},
{7, ok},
{7, ignored},
{4, ok},
{9, ok},
{11, ok},
{8, ok},
{13, ok}
{13, ignored},
{11, ok}
],
emqx_utils_stream:consume(emqx_utils_stream:mqueue(0))
).