Hello! The documentation says the following on the Busyness Method...
QUOTE If set to B[usyness] the balancer will pick the worker with the lowest current load, based on how many requests the worker is currently serving. This number is divided by the workers lbfactor, and the lowest value (least busy) worker is picked. This method is especially interesting, if your request take a long time to process, like for a download application. END QUOTE What is defined as "take a long time", is it 30 sec, 40 sec, or more ? and from the clarifications I have got from this forum, the nodes "load" is determined by it network latency using cping and cping. These I believe are used by all load-balancer methods to determine a nodes health. So checking the Requested hits (Acc in jkmanager) or Busy (Busy in jkmanager) or the Traffic are just checking the counters of a node that is more active than the other nodes. Essentially what all these methods does is check a node's health by cping, cping (Network latency) , and if it responds in good time, then check either the 'Acc', 'Busy' or 'Traffic' counters and send to the node with least 'Acc' if 'Request' method is used or "Busy" if 'Busy' method is used or "Bytes IN/OUT" if "Traffic" method is used. Is this summary of mod_jk in non-technical perspective accurate ?? Thanks Regards Mohan -- View this message in context: http://www.nabble.com/Busyness-Method-and-others...-tp14690721p14690721.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
