Project: EMQ Technologies (App Definition and Development / Streaming & Messaging)
File: e5.0.1.en.md

Add low level tuning settings for QUIC listeners. Errors returned by rule engine API are formatted in a more human readable way rather than dumping the raw error including the stacktrace. Add pod disruption budget to helm chart QUIC transport Multistreams support and QUIC TLS cacert support. Integrate `TDengine` into `bridges` as a new backend. New common TLS option 'hibernate_after' to reduce memory footprint per idle connecion, default: 5s. Validate `bytes` param to `GET /trace/:name/log` to not exceed signed 32bit integer. To prevent errors caused by an incorrect EMQX node cookie provided from an environment variable, we have implemented a fail-fast mechanism. Previously, when an incorrect cookie was provided, the command would still attempt to ping the node, leading to the error message 'Node xxx not responding to pings'. With the new implementation, if a mismatched cookie is detected, a message will be logged to indicate that the cookie is incorrect, and the command will terminate with an error code of 1 without trying to ping the node. Fix bridge metrics when running in async mode with batching enabled (`batch_size` > 1). Fix error message when the target node of `emqx_ctl cluster join` command is not running. When resources on some nodes in the cluster are still in the 'initializing/connecting' state, the `bridges/` API will crash due to missing Metrics information for those resources. This fix will ignore resources that do not have Metrics information. Fix Swagger API doc rendering crash. In version 5.0.18, a bug was introduced that resulted in duplicated field names in the configuration schema. This, in turn, caused the Swagger schema generated to become invalid. For influxdb bridge, added integer value placeholder annotation hint to `write_syntax` documentation. Also supported setting a constant value for the `timestamp` field. Improve behavior of the `replicant` nodes when the `core` cluster becomes partitioned (for example when a core node leaves the cluster). Previously, the replicant nodes were unable to rebalance connections to the core nodes, until the core cluster became whole again. This was indicated by the error messages: `[error] line: 182, mfa: mrialb:listcorenodes/1, msg: mrialbcorediscovery divergent cluster`. Fixed two bugs introduced in v5.0.18. The environment varialbe `SSLDISTOPTFILE` was not set correctly for non-boot commands. When cookie is overridden from environment variable, EMQX node is unable to start. Fix node information formatter for stopped nodes in the

The bug was introduced by v5.0.18. Fix the problem that the obfuscated password is used when using the `/bridges_probe` API to test the connection in Data-Bridge. Deprecate unused QUIC TLS options. Only following TLS options are kept for the QUIC listeners: cacertfile certfile keyfile verify Fix webhook bridge error handling: connection timeout should be a retriable error. Prior to this fix, connection timeout was classified as unrecoverable error and led to request being dropped. Fix an issue that invalid QUIC listener setting could casue segfault. Fix problem when joining core nodes running different EMQX versions into a cluster. Upgrade HTTP client ehttpc to `0.4.7`. Prior to this upgrade, HTTP clients for authentication, authorization and webhook may crash if `body` is empty but content-type HTTP header is set. For more details see . Allow 'emqx ctl cluster' command to be issued before Mnesia starts. Prior to this change, EMQX `replicant` could not use `manual` discovery strategy. Now it's possible to join cluster using 'manual' strategy. Fix bad http response format when client ID is not found in `clients` APIs Avoid parsing config files for node name and cookie when executing non-boot commands in bin/emqx. Report memory usage to statsd and prometheus using the same data source as dashboard. Prior to this fix, the memory usage data source was collected from an outdated source which did not work well in containers. Fixed configuration issue when choosing to use SSL for a Postgres connection (`authn`, `authz` and bridge). The connection could fail to complete with a previously working configuration after an upgrade from 5.0.13 to newer EMQX versions. Fix Swagger API schema generation. `deprecated` metadata field is now always boolean, as suggests. Change Kafka bridge's config `memoryoverloadprotection` default value from `true` to `false`. EMQX logs cases when messages get dropped due to overload protection, and this is also reflected in counters. However, since there is by default no alerting based on the logs and counters, setting it to `true` may cause messages being dropped without noticing. At the time being, the better option is to let sysadmin set it explicitly so they are fully aware of the benefits and risks. Use default template `${timestamp}` if the `timestamp` config is empty (undefined) when inserting data in InfluxDB. Prior to this change, InfluxDB bridge inserted a wrong timestamp when template is not provided.