MTE Relay v5.0.6: load balancer idle timeout
· 2 min read
MTE Relay 5.0.6 is a patch release of MTE Relay Server and MTE API Relay. It
changes how long a relay keeps an idle keep alive connection open and corrects
the mobile SDK versions in the 478 message. v5 clients and configuration
work unchanged.
Load balancer idle timeout
- Relay 5.0.5 and earlier closed an idle keep alive connection after a fixed
60 seconds. Load balancers that reuse idle connections to their backends
for longer could send a request on a connection the relay had just closed
and answer it with their own
502. The OCI load balancer holds idle backend connections for 300 seconds and asks backends to keep them for at least 310, so deployments there saw occasional502answers after quiet periods. An AWS Application Load Balancer at its 60 second default raced the relay's 60. - The relay now keeps an idle connection for
HTTP_IDLE_TIMEOUT_SECONDS, 620 by default. That outlives OCI, AWS Application Load Balancers at their default, and ingress-nginx at its default. Raise it above the idle time of a balancer that holds connections longer, such as an Envoy based gateway or an ALB set above 620.0takes the default; a negative value refuses to start. It is a restart setting, and the control plane shows it under Server. See Load balancers and proxies. - SocketX reads the same variable with the same default and rule.
Minimum mobile SDK versions in the 478 message
- A
478 frame_version_unsupportedanswer ends with the minimum SDK versions that speak frame version 2. Relay 5.0.5 and earlier named Android and iOS 5.0.0, but the mobile SDKs first spoke frame version 2 in 5.3.0. The message now readsminimum SDK versions: android 5.3.0, ios 5.3.0, browser 5.0.0, go relay 5.0.0. Only the text changed. See Discovery.
Upgrading
Change the image tag to 5.0.6 on the control plane and every relay, control
plane first. Relays keep serving their last configuration while it restarts.
Nothing else changes.