Load based routing load balancing

This topic pertains to a clustered listener configuration. To achieve load balancing, Unica Campaign uses a load based routing algorithm. This algorithm maintains a weighted list of servers, where a heavier (higher) weight indicates preference.

Each node in a cluster can process a portion of the total application traffic. The loadBalanceWeight configuration setting and current execution load on the listener determines how transactions are allocated to clustered nodes.Before allocating every new connection to the listener , it looks at the load of server processes running on the listener and listener's assigned weight.As a result, traffic is distributed fairly and efficiently to the listeners, that you rank as being more capable of handling requests.

The loadBalanceWeight assigns a relative value to each node. A higher value gives a node a greater proportion of the load, so more transactions are given to that listener. Lower values are assigned to less powerful or more heavily loaded machines, so fewer transactions are sent to those listeners. A value of 0 prohibits a listener from processing any transactions and typically is not used.

Starting Campaign 12.0, load balancing feature is enabled for Unica Optimize as well. When multiple optimize sessions are executed at a time, load of the session execution is fairly distributed to the listeners, based on current load and weight of the listener.

For details and an example, see the topic that explains the Campaign|unicaACListener|node[n]|loadBalanceWeight configuration setting.

If you change the loadBalanceWeight, run the unica_svradmrefresh command to inform the master listener of the change.

For details, see the topic that explains the Campagin|unicaACListener|node[n]| listenerType configuration settings.