Zhongwen Deng 3 лет назад
Родитель
Сommit
a05b7bf555
2 измененных файлов с 5 добавлено и 5 удалено
  1. 4 4
      CHANGES-5.0.md
  2. 1 1
      apps/emqx_conf/src/emqx_cluster_rpc.erl

+ 4 - 4
CHANGES-5.0.md

@@ -19,6 +19,7 @@
 * Improve the dashboard listener startup log, the listener name is no longer spliced with port information,
 * Improve the dashboard listener startup log, the listener name is no longer spliced with port information,
   and the colon(:) is no longer displayed when IP is not specified. [#8480](https://github.com/emqx/emqx/pull/8480)
   and the colon(:) is no longer displayed when IP is not specified. [#8480](https://github.com/emqx/emqx/pull/8480)
 * Remove `/configs/listeners` API, use `/listeners/` instead. [#8485](https://github.com/emqx/emqx/pull/8485)
 * Remove `/configs/listeners` API, use `/listeners/` instead. [#8485](https://github.com/emqx/emqx/pull/8485)
+* Optimize performance of builtin database operations in processes with long message queue [8439](https://github.com/emqx/emqx/pull/8439)
 
 
 # 5.0.3
 # 5.0.3
 
 
@@ -32,17 +33,16 @@
 ## Enhancements
 ## Enhancements
 
 
 * Improve the speed of dashboard's HTTP API routing rule generation, which sometimes causes timeout [#8438](https://github.com/emqx/emqx/pull/8438)
 * Improve the speed of dashboard's HTTP API routing rule generation, which sometimes causes timeout [#8438](https://github.com/emqx/emqx/pull/8438)
-* Optimize performance of builtin database operations in processes with long message queue [8439](https://github.com/emqx/emqx/pull/8439)
 
 
 # 5.0.2
 # 5.0.2
 
 
-Announcemnet: EMQX team has decided to stop supporting relup for opensouce edition.
-Going forward, it will be an enterprise only feature.
+Announcement: EMQX team has decided to stop supporting relup for opensource edition.
+Going forward, it will be an enterprise-only feature.
 
 
 Main reason: relup requires carefully crafted upgrade instructions from ALL previous versions.
 Main reason: relup requires carefully crafted upgrade instructions from ALL previous versions.
 
 
 For example, 4.3 is now at 4.3.16, we have `4.3.0->4.3.16`, `4.3.1->4.3.16`, ... 16 such upgrade paths in total to maintain.
 For example, 4.3 is now at 4.3.16, we have `4.3.0->4.3.16`, `4.3.1->4.3.16`, ... 16 such upgrade paths in total to maintain.
-This had been the biggest obstacle for EMQX team to act agile enough in deliverying enhancements and fixes.
+This had been the biggest obstacle for EMQX team to act agile enough in delivering enhancements and fixes.
 
 
 ## Enhancements
 ## Enhancements
 
 

+ 1 - 1
apps/emqx_conf/src/emqx_cluster_rpc.erl

@@ -263,7 +263,7 @@ fast_forward_to_commit(Node, ToTnxId) ->
 %% @private
 %% @private
 init([Node, RetryMs]) ->
 init([Node, RetryMs]) ->
     %% Workaround for https://github.com/emqx/mria/issues/94:
     %% Workaround for https://github.com/emqx/mria/issues/94:
-    mria_rlog:wait_for_shards([?CLUSTER_RPC_SHARD], 1000),
+    _ = mria_rlog:wait_for_shards([?CLUSTER_RPC_SHARD], 1000),
     _ = mria:wait_for_tables([?CLUSTER_MFA, ?CLUSTER_COMMIT]),
     _ = mria:wait_for_tables([?CLUSTER_MFA, ?CLUSTER_COMMIT]),
     {ok, _} = mnesia:subscribe({table, ?CLUSTER_MFA, simple}),
     {ok, _} = mnesia:subscribe({table, ?CLUSTER_MFA, simple}),
     State = #{node => Node, retry_interval => RetryMs},
     State = #{node => Node, retry_interval => RetryMs},