In most production deployments, it is desirable to configure a load balancer in front of the cluster. This topic discusses the considerations for this load balancer.
This topic discusses the load balancer in front of the cluster (the load balancer with the callout):
If you add nodes to the cluster, you must update the configuration of the load balancer with the host names and ports of the added Oracle Endeca Servers.
For the duration of an outer transaction (which may include updates sent to the leader node), the load balancer continues sending requests to all nodes in the cluster, including the leader node.
Configuring session affinity also helps minimize consistency problems as updates propagate from the leader to the follower nodes in the cluster (if you are not using outer transactions to run updates).
For information on configuring the data sources in Studio that allow access to any node in the cluster through a load balancer, and access to the leader node for sending updating requests, see the Oracle Endeca Information Discovery Studio User's Guide.