求助：lb worker的4种method的区别和用处

xxt_emo17

看了下官网关于worker. properties的配置说明，对其中关于lb worker的method属性不太理解
分别是request、session、traffic、busyness。
谁能给解释下4者的工作方式和应用？

尤其是用在什么地方合适！

[ 本帖最后由 xxt_emo17 于 2008-5-28 10:04 编辑 ]

hmglly

你把官方文档中这三个方法的解释贴在这里，让大家帮你翻译或者解释一下

xxt_emo17

If method is set to R[equest] the balancer will use number of requests to find the best worker. Accesses will be distributed according to the lbfactor in a sliding time window. This is the default value and should be working well for most applications.

If method is set to S[ession] the balancer will use number of sessions to find the best worker. Accesses will be distributed according to the lbfactor in a sliding time window. Because the balancer does not keep any state, it actually does not know the number of sessions. Instead it counts each request without a session cookie or URL encoding as a new session. This method will neither know, when a session is being invalidated, nor will it correct its load numbers according to session timeouts or worker failover. This method should be used, if sessions are your limiting resource, e.g. when you only have limited memory and your sessions need a lot of memory.

If set to T[raffic] the balancer will use the network traffic between JK and Tomcat to find the best worker. Accesses will be distributed according to the lbfactor in a sliding time window. This method should be used, if network to and from the backends is your limiting resource.

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.