On Fri, Aug 4, 2017 at 11:49 PM, Christopher Schultz < ch...@christopherschultz.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Martin, > > On 8/4/17 4:53 AM, Martin Knoblauch wrote: > > Hi, > > > > just need some clarification on the mod_jk load blanacing method > > "Next". The documentation states: > > > > "If method is set to N[ext] the balancer will again use the number > > of sessions to find the best worker. All remarks concerning the > > Session method apply as well. The difference to the Session method > > is how the session count is handled in the sliding time window. The > > Next method does not divide by 2, instead it subtracts the current > > minimum number. This should effectively result in a round-robin > > session balancing, thus the name Next. Under high load, the two > > session balancing methods will result in a similar distribution, > > but Next will be better if you need to distribute small numbers of > > sessions. " > > > > What exactly is the "current minimum number"? How is the minimum > > taken? > >> From all workers in the balancer set, or only the ACTive ones? > > I don't know for sure, but just in case this is a language issue, I > believe it means it will subtract the "lowest number of sessions > amongst all active workers". So if you had workers 1, 2, and 3 with > 45, 50, and 55 sessions respectively, it will subtract the value 45 > from all worker session counts to determine the priority for which > node will get the next session. > > Now my question was: which workers are considered for the lowest number of sessions. All of them, or only the ones in ACT state? Thanks Martin > > -- ------------------------------------------------------ Martin Knoblauch email: k n o b i AT knobisoft DOT de www: http://www.knobisoft.de
