Load Balancing
Overview
Load balancing across multiple application server is a commonly used technique for optimizing resource utilization, maximizing throughput, reducing latency, and ensuring fault‑tolerant configurations. Users can configure the load balancing settings, select desired load balancing algorithem, enable SSL while forwarding the data towards backend, etc. under this section.
Load Balancing Algorithms
This field specifies the load balancing algorithm according to the configured website.
ROUND ROBIN: This algorithm is a smart approach to distribute client requests across an array of servers. It forwards the client request to each server in turn. Also, assigns a weight to each server as per current load and idle capacity.
LEAST CONNECTIONS: This algorithm is a dynamic load balancing algorithm. It forwards client requests to the server, which has the least no. of active connections on the server.
LEAST RESPONSE TIME : This load balancing algorithem is used to provide the response from the server which has the less response time. Suppose there are two servers in the backend which have repsonse time A and B. A is less than B. In this case, Haltdos WAF Solution will give preference to the server which is having less response time than others.
LEAST BANDWIDTH : This load balancing algorithem is used to load balance as per the bandwidth available for the backend to handle the load coming from the client side.
IP HASH: This algorithm takes the client's and server's source and destination IP address to generate a unique hash key. This key is used to assign the client to a specific server. In the case of a broken session, the key can be regenerated, and the client can be directed to the same server.
LEAST REQUEST: This algorithm is a dynamic load balancing algorithm. It forwards client requests to the server, which have served the minimum amount of requests.
How to use:
- Go to WAF > Server Farm > Load Balancing
- Set the configurations and Save Changes.
Parameters | Accepted value | Default |
---|---|---|
Encrypt to Upstream | Boolean | False |
Upstream Retries | Integer | 1 |
Failover Threshold | Integer | 50 |
Load Balancing Algorithm | Drop-down | Least Connection |
Sticky Session Cookie | String | Blank |
Description
Encrypt to Upstream
This option allows users to specify if WAF should re-encrypt traffic before sending to servers
Upstream Retries
This option specify the upstream retries. By default, the value is set to 1.
Fail-over Threshold
This option specify the fail-over threshold in percentage of (active/total) primary servers for switching to backup servers. By default, the value is set to 50%.
Load Balancing Algorithm
This drop-down specify the algorithm used by the server group. By default, the value is selected as Round Robin.
Sticky Session Cookie
The users are allowed to specify enabling sticky session based on specified cookie