Load balancing considerations

It is recommended that a load balancer is used in front of ECS.

NOTE:

In HDD and NVMe intermix deployment, configure load balancer to forward the requests of HDD bucket to HDD nodes and forward the requests of NVMe bucket to NVMe nodes. If load balancer cannot be configured as required, contact ECS Remote Support to enable data forward for S3 server
```
com.emc.ecs.objheadsvc.need_forward_request
```
.
In HDD and NVMe intermix deployment, configure clients to make them access NVMe bucket through NVMe node and access HDD bucket through HDD node. If mixed accesses are inevitable, contact ECS Remote Support to enable data forward for S3 server
```
com.emc.ecs.objheadsvc.need_forward_request
```
.

In addition to distributing the load across ECS cluster nodes, a load balancer provides High Availability (HA) for the ECS cluster by routing traffic to healthy nodes. Where network separation is implemented, and data and management traffic are separated, the load balancer must be configured so that user requests, using the supported data access protocols, are balanced across the IP addresses of the data network. ECS Management REST API requests can be made directly to a node IP on the management network or can be load that is balanced across the management network for HA.

The load balancer configuration depends the load balancer type. For information about tested configurations and best practice, contact ECS Remote Support.