From 9bafc1c997c7ebab73b8e1a7a22f2040019b6c0a Mon Sep 17 00:00:00 2001 From: Shawn <506895667@qq.com> Date: Tue, 11 Apr 2023 17:26:57 +0800 Subject: [PATCH] chore: improve the change logs --- changes/v4.4.17-en.md | 2 +- changes/v4.4.17-zh.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/changes/v4.4.17-en.md b/changes/v4.4.17-en.md index efbfdb189..c1c96a4d8 100644 --- a/changes/v4.4.17-en.md +++ b/changes/v4.4.17-en.md @@ -37,7 +37,7 @@ - Fixed MQTT bridge TLS connection could not verify wildcard certificate from peer [#10094](https://github.com/emqx/emqx/pull/10094). - Fixed the problem that EMQX could not timely clear the disconnected MQTT connection information due to a large number of retained messages [#10189](https://github.com/emqx/emqx/pull/10189). - Before this fix, the `emqx_retainer` plugin and the connection cleanup process of emqx shared the same process pool. + Before this fix, the `emqx_retainer` plugin and the connection cleanup process of EMQX shared the same process pool. Therefore, if the process pool was blocked by a large number of retain messages, many disconnected MQTT connections would not be cleaned up in time. For more details, see [#9409](https://github.com/emqx/emqx/issues/9409). In this fix, we created a separate process pool for the `emqx_retainer` plugin to avoid this problem. diff --git a/changes/v4.4.17-zh.md b/changes/v4.4.17-zh.md index 737ff92f7..cbf763128 100644 --- a/changes/v4.4.17-zh.md +++ b/changes/v4.4.17-zh.md @@ -8,7 +8,7 @@ ``` [error] supervisor: 'esockd_connection_sup - <0.3265.0>', errorContext: connection_shutdown, reason: {recv_proxy_info_error,tcp_closed}, offender: ``` - 次修复之后不再打印任何日志，但仍然可以通过 `emqx_ctl listeners` 命令来查看错误原因的统计。 + 此修复之后不再打印任何日志，但仍然可以通过 `emqx_ctl listeners` 命令来查看错误原因的统计。 - 改进监听器出现文件描述符耗尽错误时的日志 [emqx/esockd#173](https://github.com/emqx/esockd/pull/173)。 之前的日志： @@ -35,7 +35,7 @@ - 修正了 MQTT 桥接 TLS 连接无法验证对端的带通配符的证书 [#10094](https://github.com/emqx/emqx/pull/10094)。 - 修复由于大量 retain 消息导致 EMQX 无法及时清除已掉线的 MQTT 连接信息的问题。[#10189](https://github.com/emqx/emqx/pull/10189)。 - 在此修复之前，`emqx_retainer` 插件和 emqx 的连接信息清理过程共用了同一个进程池，所以 + 在此修复之前，`emqx_retainer` 插件和 EMQX 的连接信息清理过程共用了同一个进程池，所以 如果该进程池被大量的 retain 消息下发任务阻塞时，许多已经掉线的 MQTT 连接将得不到及时清理。 问题详情见 [#9409](https://github.com/emqx/emqx/issues/9409)。 在此修复中，我们给 `emqx_retainer` 插件创建了单独的进程池，从而避免了该问题。