Kbase P39013: When using NameServer load balancing, if there is 1 BUSY agent on a broker, where will the NameServe
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/20/2009 |
|
Status: Verified
GOAL:
When using NameServer load balancing, if there is 1 BUSY agent on a broker, where will the NameServer re-route the next request?
GOAL:
Does the NameServer know which agents are BUSY on multiple brokers?
GOAL:
Does NameServer load balance by broker status or by number of requests?
FACT(s) (Environment):
All Supported Operating Systems
FIX:
The NameServer's routing is based upon the number of request, depending on the priorityWeight of the brokers that provide a service. The NameServer has no idea which brokers have BUSY agents. The NameServer does not hold agent information. If the priorityWeight for all the brokers is 0, then the load will be distributed "evenly" between the brokers. Request do not necessarily alternate between brokers, but the load will end up being split roughly evenly.
In a situation where you have 2 brokers with only 1 agent;
wsbroker1 wsbroker2
agent1 agents2
If AGENT1 (on wsbroker1) is BUSY, then the next request may not always go to wsbroker2/agents2. The next request may go to wsbroker1/agents1 where it will have to wait until the first request is complete, even if wsbroker2/agent2 is available.
More information on this matter can be found within the WebSpeed Installation and Configuration Guide, chapter "Understanding the NameServer's Load Balancing Option".
-Percentage Weight Factors
-Arbitrary Weight Factors
-Fail-over Weight Factor