fix: increase emqx_router_sup restart intensity

The goal is to tolerate occasional crashes that can happen under relatively normal conditions
and don't seem critical to shutdown the whole app (emqx).
For example, mria write/delete call delegated from a replicant to a core node may fail,
if the core node is being stopped / restarted / not ready.

Fixes: EMQX-10703, #11310
This commit is contained in:
Serge Tupchii 2023-08-03 13:24:22 +03:00
parent 1b0b15786c
commit f276ea9e91
3 changed files with 13 additions and 2 deletions

View File

@ -2,7 +2,7 @@
{application, emqx, [ {application, emqx, [
{id, "emqx"}, {id, "emqx"},
{description, "EMQX Core"}, {description, "EMQX Core"},
{vsn, "5.1.4"}, {vsn, "5.1.5"},
{modules, []}, {modules, []},
{registered, []}, {registered, []},
{applications, [ {applications, [

View File

@ -41,4 +41,9 @@ init([]) ->
hash, hash,
{emqx_router, start_link, []} {emqx_router, start_link, []}
]), ]),
{ok, {{one_for_all, 0, 1}, [Helper, RouterPool]}}. SupFlags = #{
strategy => one_for_one,
intensity => 10,
period => 100
},
{ok, {SupFlags, [Helper, RouterPool]}}.

View File

@ -0,0 +1,6 @@
Increase `emqx_router_sup` restart intensity.
The goal is to tolerate occasional crashes that can happen under relatively normal conditions
and don't seem critical to shutdown the whole app (emqx).
For example, mria write/delete call delegated from a replicant to a core node by `emqx_router_helper` may fail,
if the core node is being stopped / restarted / not ready.