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

chore: add a warning log if conflict is detected

This commit is contained in:
zmstone 2024-03-25 17:07:56 +01:00
parent d32a1a892a
commit b8b0b809b4
1 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
apps/emqx/src/emqx_router.erl
View File

@ -750,9 +750,19 @@ choose_schema_vsn(ConfSchema, ClusterSchema, State) ->
_Conflicting when ClusterSchema =/= undefined -> _Conflicting when ClusterSchema =/= undefined ->
%% There are existing records in both v1 and v2 schema, %% There are existing records in both v1 and v2 schema,
%% we have to use what the peer nodes agreed on. %% we have to use what the peer nodes agreed on.
%% because it could be HTIS node which caused cnoflict. %% because it could be THIS node which caused the cnoflict.
%% %%
%% The stale records will be left-over, but harmless %% The stale records will be left-over, but harmless
Desc =
"Conflicting schema version detected for routing records, but "
"all the peer nodes are running the same version, so this node "
"will use the same schema but discard the harmless stale records. "
"This warning will go away after the next full cluster (non-rolling) restart.",
?SLOG(warning, #{
msg => "conflicting_routing_storage_detected",
resolved => ClusterSchema,
description => Desc
}),
ClusterSchema; ClusterSchema;
_Conflicting -> _Conflicting ->
Desc = schema_conflict_reason(records, State), Desc = schema_conflict_reason(records, State),