Weighted round robin load balancing

This topic pertains to a clustered listener configuration. To achieve load balancing, HCL® Campaign uses a weighted round robin 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 determines how transactions are allocated to clustered nodes. New connections are forwarded in proportion to each node's assigned weight. As a result, traffic is distributed more efficiently to the servers 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.

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_svradm refresh command to inform the master listener of the change.