Client load balancing helps distribute new connections in your environment so that no one server is overwhelmed with connection requests. When both connection failover and client load balancing are enabled, the first connection attempt establishes the random order in which primary and alternate OpenAccess SDK Servers are tried. Subsequent connection attempts use the same sequence. For example, suppose that client load balancing is enabled as shown in Figure 8.
Figure 8: Client Load Balancing Example
First, OpenAccess SDK Server B is tried (1). Then, Server C may be tried (2), followed by a connection attempt to Server A (3); subsequent connection attempts use this same sequence. In contrast, if client load balancing was not enabled in this scenario, each OpenAccess SDK Server would be tried in sequential order, primary server first, then alternate servers based on their entry order in the alternate servers list.
Refer to the OpenAccess SDK Administrator’s Guide for more information about connection failover.
