If you have chosen the Least Weighted Current Report Sets (Weighted Min-load) (loadbalance.type=2 in the server.properties file) algorithm for load balancing, you will have to configure a performance weight for each clustered server on the admin server. The higher performance weight you set to a clustered server, the higher chance it may get selected by the admin server during load balancing.
You can use the Test button to get the current performance weight of each clustered servers.
Click OK to save the weight values.
Example 1 - when there are free servers:
| Active Servers | ServerA | ServerB | ServerC | Comments |
|---|---|---|---|---|
| Is local server | TRUE | FALSE | FALSE | |
| Maximum concurrent report sets | 8 | Unlimited | 5 | |
| Number of currently running report sets | 6 | 6 | 5 | |
| Performance weight | 10 | 10 | 10 | |
| Calculation | ||||
| Weighted current report sets | 0.6 | 0.6 | 0.5 | |
| Is free | TRUE | TRUE | FALSE | Current < MaxConcurrent, or MaxConcurrent is unlimited |
| Candidate servers | YES | YES | Select from free servers | |
| Candidate servers | YES | YES | Select servers which have the least Weighted current report sets | |
| Selected server | YES | Local server has higher priority | ||
Example 2 - when there are no free servers:
| Active Servers | ServerA | ServerB | ServerC | Comments |
|---|---|---|---|---|
| Is local server | TRUE | FALSE | FALSE | |
| Maximum concurrent report sets | 10 | 10 | 10 | |
| Number of currently running report sets | 10 | 10 | 10 | |
| Performance weight | 4 | 5 | 8 | |
| Calculation | ||||
| Weighted current report sets | 2.5 | 2 | 1.25 | |
| Is free | FALSE | FALSE | FALSE | Current < MaxConcurrent, or MaxConcurrent is unlimited |
| Candidate servers | YES | YES | YES | Selects from all servers when all servers are full |
| Candidate servers | YES |
Select servers which have the least Weighted current report sets |
||
| Selected server | YES | Select ServerC | ||