Configuring Front End Idle Timeout for Gorouter and HAProxy
Page last updated:
Warning: Pivotal Application Service (PAS) v2.8 is no longer supported because it has reached the End of General Support (EOGS) phase as defined by the Support Lifecycle Policy. To stay up to date with the latest software and security updates, upgrade to a supported version.
This topic describes how to configure the Front end idle timeout for the Gorouter and HAProxy field in the Networking pane of the Pivotal Application Service (PAS) tile.
You can optionally use the Front end idle timeout for the Gorouter and HAProxy field to help prevent connections from your load balancer to the Gorouter or HAProxy from being closed prematurely. The value you enter sets the duration, in seconds, that the Gorouter or HAProxy maintains an idle open connection from a load balancer that supports keep-alive.
In general, set the value higher than your load balancer’s back end idle timeout to avoid the race condition where the load balancer sends a request before it discovers that the Gorouter or HAProxy has closed the connection.
For specific guidance and exceptions to this rule, see the table below:
|AWS||AWS ELB has a default timeout of 60 seconds, so Pivotal recommends a value greater than
|Azure||By default, Azure load balancer times out at 240 seconds without sending a TCP RST to clients, so as an exception, Pivotal recommends a value lower than
|GCP||GCP has a default timeout of 600 seconds. For GCP HTTP load balancers, Pivotal recommends a value greater than
|Other||Set the timeout value to be greater than that of the load balancer’s back end idle timeout.|