![]() ![]() Improved error logs related to Proxy Protocol emqx/esockd#177 (opens new window).Īdded a new feature to enable partial certificate chain validation for TLS listeners #10553 (opens new window).įor details, please check out the _chain in the nf config file.Īdded a new feature to enable client certificate extended key usage validation for TLS listeners #10669 (opens new window).įor details, please check out the _peer_ext_key_usage in the nf config file.Īdded the live_connections field in the HTTP API /api/v4/nodes response #10859 (opens new window). This configuration is only effective on Linux and MacOS systems. ![]() Users can enable the TCP layer's Keep Alive feature and specify time parameters using this configuration. You can still opt to set auto_reconnect = false to turn off the automatic reconnection feature.Īdded TLS connection support to RabbitMQ resource.Īdded support for defining attributes and ordering key for GCP PubSub actions.įixed the issue that the mongo_date() function of the rule engine cannot be tested on the Dashboard.īefore the fix, mongo_date() can be used normally, but an error will occur when testing on the SQL test page of the Dashboard.įixed the issue where the rule engine failed to send messages through RabbitMQ actions after a hot upgrade to version 4.4.19.Īdded support for TCP keep-alive in MQTT/TCP and MQTT/SSL listeners #10854 (opens new window).Ī new configuration option has been added: zone.tcp_keepalive = Idle,Interval,Probes. With this new enhancement, EMQX can reconnect automatically. Setting message_accumulation_size = 0 (default value) will disable this message buffering feature.Īdded the auto_reconnect option for SQL Server resources.īefore this improvement, when the connection between EMQX and the SQL Server database was disrupted, EMQX was unable to reconnect automatically. The driver will then handle the forwarding to Kafka or HStreamDB services. When the number of cached messages reaches message_accumulation_size or the time interval reaches message_accumulation_interval, the buffered messages will be batched and sent to the Kafka or HStreamDB driver. Now, messages sent from EMQX to Kafka or HStreamDB drivers will first enter the buffer. This optimization comes at the expense of increased message latency, but it significantly enhances the throughput capacity when sending data to Kafka and HStreamDB. ![]() This enhancement added an Erlang message buffer ahead of the driver process, reducing the frequency of internal message passing within EMQX. Improved the performance of sending data to Kafka and HStreamDB. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |