Incompatible Changes in EMQX 5.10
5.10.1
- #15752 Listener connection rate limits (
max_conn_rate
andmax_conn_burst
) are now enforced per listener rather than per acceptor, restoring the pre-5.9.0 behavior. As a result, configurations from versions 5.9.0, 5.9.1, and 5.10.0 are incompatible: specified rates must be scaled up by the number of acceptors configured for respective listeners.
5.10.0
#15289 Added a new
resource_opts.health_check_timeout
configuration to all Connectors, Actions, and Sources, with a default value of 60 seconds. If a health check takes more than this to return a response, the Connector/Action/Source will be deemeddisconnected
.Note: since the default is 60 seconds, this means that if a Connector/Action/Source previously could take more than that to return a healthy response, now it'll be deemed disconnected in such situations.
#15286 Configuration option
broker.routing.storage_schema
is now deprecated and ignored. Legacyv1
routing storage schema is no longer supported, and EMQX will refuse to start in a cluster running older versions that still use it. For instructions on upgrading a cluster that usesv1
routing schema, see Rolling Upgrade Considerations for EMQX 5.10 or Later.#15239 The type for the
multi_tenancy.default_max_sessions
is now eitherinfinity
or a positive integer. Previously,0
would be accepted.#15156 Schema validation was added to
dashboard.sso.oidc.issuer
field. Now, this value is checked to be a valid URL.