chore: improve the change logs
This commit is contained in:
parent
aa683e95a1
commit
9768b8112d
|
@ -4,7 +4,7 @@
|
|||
|
||||
- Remove the error logs from the listeners with `Proxy Protocol` enabled when receiving TCP port probes [emqx/esockd#172](https://github.com/emqx/esockd/pull/172).
|
||||
|
||||
Before this change, if the listener has enabled the Proxy Protocol (`listener.tcp.external.proxy_protocol=on`),
|
||||
Before this change, if the listener has enabled the `Proxy Protocol` (`listener.tcp.external.proxy_protocol=on`),
|
||||
and if the connection get disconnected right after the TCP handshake is completed and before the ProxyInfo is received, the following error log will be printed:
|
||||
```
|
||||
[error] supervisor: 'esockd_connection_sup - <0.3265.0>', errorContext: connection_shutdown, reason: {recv_proxy_info_error,tcp_closed}, offender:
|
||||
|
|
|
@ -3,24 +3,24 @@
|
|||
## 增强
|
||||
|
||||
- 启用了 `Proxy Protocol` 的监听器在收到 TCP 端口探测时,不再打印错误日志 [emqx/esockd#172](https://github.com/emqx/esockd/pull/172)。
|
||||
在此修复之前,如果监听器开启了 Proxy Protocol (`listener.tcp.external.proxy_protocol = on`),
|
||||
并且在 TCP 握手完成之后、收到 ProxyInfo 之前连接就被断开了,会打印下面一行错误日志:
|
||||
修复前,如果监听器已启用了代理协议 (`listener.tcp.external.proxy_protocol = on`),
|
||||
但连接在 TCP 握手完成之后、收到代理信息之前就被断开了,则会打印下面一行错误日志:
|
||||
```
|
||||
[error] supervisor: 'esockd_connection_sup - <0.3265.0>', errorContext: connection_shutdown, reason: {recv_proxy_info_error,tcp_closed}, offender:
|
||||
```
|
||||
此修复之后不再打印任何日志,但仍然可以通过 `emqx_ctl listeners` 命令来查看错误原因的统计。
|
||||
|
||||
- 改进监听器出现文件描述符耗尽错误时的日志 [emqx/esockd#173](https://github.com/emqx/esockd/pull/173)。
|
||||
之前的日志:
|
||||
之前的错误日志为:
|
||||
```
|
||||
[error] Accept error on 0.0.0.0:1883: emfile
|
||||
```
|
||||
改进之后:
|
||||
现在改为:
|
||||
```
|
||||
[error] Accept error on 0.0.0.0:1883: EMFILE (Too many open files)
|
||||
```
|
||||
|
||||
- 提升规则数量较多时规则引擎的执行性能 [#10283](https://github.com/emqx/emqx/pull/10283)
|
||||
- 提升规则引擎在规则数量较多时的执行性能 [#10283](https://github.com/emqx/emqx/pull/10283)
|
||||
在此改动之前,当规则数量比较多的时候,规则引擎的执行会成为瓶颈,规则引擎将耗费大量 CPU 在规则的查询和匹配上。
|
||||
本次优化中,通过简单地给规则列表添加一个缓存,大幅提升了此场景下的规则执行效率。
|
||||
在我们的测试中,在一个 32 核 32G 的虚拟机上,我们创建了 700 条不执行任何动作的规则(绑定了 "do_nothing" 调试动作),
|
||||
|
|
Loading…
Reference in New Issue