Update image public.ecr.aws/emqx/emqx to v5.8.3 #941
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/public.ecr.aws-emqx-emqx-5.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
5.8.2->5.8.3Release Notes
emqx/emqx (public.ecr.aws/emqx/emqx)
v5.8.3: EMQX v5.8.3Compare Source
v5.8.3
Make sure to check the breaking changes and known issues before upgrading to EMQX 5.8.3.
Enhancements
Core MQTT Functionalities
#14219 Enhanced Connection Rate Limiter for Improved System Resilience.
Improved system stability and responsiveness under high connection rates: Previously, when the connection rate limit was exceeded, listener acceptors would ignore new connection attempts, potentially resulting in an unrecoverable state if a large number of clients connected or reconnected frequently within a short period. Listeners now accept pending connections but immediately close them if the rate limit is reached. This reduces resource strain and improves system resilience during peak loads.
New listener option
nolingerintroduced: When set totrue, a TCP-RST is sent immediately upon socket closure, helping to mitigate SYN flood attacks and further enhancing connection-handling efficiency.max_connectionconfiguration for MQTT listeners now capped by system limits: Themax_connectionvalue for MQTT listeners is now constrained by the system's limits (e.g.,ulimitfrom the OS andnode.process_limit). If configured toinfinityor a value greater than the system limit, it will automatically be adjusted to match the system's maximum limit.SSL listeners'
ssl_optionsnow validated before changes: Previously, invalid SSL options (such as unsupported TLS versions) could be accepted, causing client connection failures after a listener reconfiguration. With this update:400status code.Configuration
#14195 Added support for client ID override.
EMQX now provides greater flexibility by allowing custom client ID overrides using the
mqtt.clientid_override={Expression}configuration. This introduces a more dynamic approach to client ID management. As part of this update, theuse_userid_as_clientidandpeer_cert_as_clientidoptions are deprecated, though they will remain available for compatibility until version 6.0.MQTT over QUIC
quicerto 0.1.9.Bug Fixes
Core MQTT Functionalities
check_gcwarning from appearing when a WebSocket connection encounters a rate limit.error: {{case_clause,#{invalid_property_code => 51}},[{cowboy_websocket...}}.emqttfrom version 1.13.0 to 1.13.5. For more details, please refer to the emqtt changelog.Durable Sessions
$symbol, in accordance with the MQTT specification.REST API
Usersendpoint was incorrectly listed as supportingBasicAuthentication.Data Integration
#14172 Resolved a potential race condition where testing a connector using the HTTP API could leave lingering resources if the HTTP request timed out.
#14178 Fixed an issue where configuration synchronization could become stuck on a particular node due to simultaneous deletion of rules across different nodes in the cluster.
#14226 Mitigated a scenario where, under high load, a node could lose track of resource metrics (e.g., action/source) and fail to recover without a restart. Now, when restarting a resource or resetting its metrics, the system attempts to recreate the lost metrics.
Additionally, warning logs related to metric failures, such as those for "hot-path" metrics like
matched, are now throttled to prevent excessive log flooding. Example of throttled log:#14265 Fixed an issue where a
badkeyerror would occur when stopping a connector if the MQTT Source action failed to subscribe successfully.#14296 Prevented
ecpool_supfrom being blocked by a slow-startingecpool_worker.Configuration
#14180 Fixed an issue with variform expressions returning
'undefined'when a variable is bound to the valueundefinedornull. Now, an empty string is returned instead.#14289 Resolved a log file path issue when importing configurations from a different environment. The
EMQX_LOG_DIRenvironment variable is set to/opt/emqx/login Docker but/var/log/emqx/when installed via RPM/DEB packages. Prior to this fix, log file paths (default file handler and audit handler) are environment-variable interpolated when being exported. This could cause crashes when importing configs into a different environment where the directory didn’t exist.With this fix, log file paths are no longer environment-variable interpolated during export. Additionally, absolute log directory paths from older versions are now converted back to environment variables if the path doesn’t exist in the new environment.
Extension
client.connecthook was not being triggered for some gateways.MQTT over QUIC
#14258 Reduced the QUIC connection shutdown timeout. Previously, QUIC connections had a 5-second timeout for graceful shutdown. If the client was unresponsive, EMQX would log warnings like:
or potentially cause a timeout on the Dashboard when attempting to disconnect the client. The timeout has now been reduced to 1 second for "kick" actions and 3 seconds for other scenarios.
Breaking Changes
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Renovate Bot.