Load Balancer Session

News Knowledge Base
1

Different load balancing session timeout.

Load balancer Session: The exact configurations can depend on environment, infrastructure, and the specific load balancer solution being used.

Persisting Session Time: When users are accessing Orchestrator through a load balancer, it is important to ensure that their session state is maintained consistently, even if their requests are being routed to different servers. This can often be achieved through a mechanism called "session persistence" or "sticky sessions."

The recommended session persistence time depends on your application's usage patterns and the expected session duration. A typical range could be anywhere from 15 minutes to an hour. This setting should be determined based on factors such as behavior, session expiration times, and server load.

Web Socket Time: Web Socket is a protocol that enables full-duplex communication between a client and a server over a single, long-lived connection.

Ideally it works with default configurations. There is generally no need to set a specific Web Socket timeout, as Web Socket connections can remain open for as long as they're needed. Timeout Settings:

Timeout settings are crucial to ensure that requests are not prematurely terminated and users have a seamless experience.

  1. Connection Timeout: This specifies how long the load balancer should wait for a connection to be established to the backend server. Set this value based on the expected response time of your backend servers. A common value is 30 seconds.
  2. Request Timeout: This defines how long the load balancer should wait for the entire request to be processed by the backend server. This should be set based on the maximum time your application requires to process a request. A common value is 60 seconds.
  3. Idle Timeout: This determines how long a connection can remain idle before the load balancer closes it. Set this value to avoid resource wastage due to open but inactive connections. A common value is 5 minutes.
  4. Session Persistence Timeout: If you're using session persistence (sticky sessions), ensure that the timeout aligns with the session expiration policy in your application. Users should remain connected to the same server until their session expires.

Note: These timeout values are just recommendations and can vary based on the application's behavior and infrastructure. In those scenarios it is highly recommended to involve IT or infrastructure team. They can provide insights and guidance tailored to the specific environment and configurations.