|
Hello,
Octave wrote:
Hi,
Working on 2.2.X with ipvs version 1.0.8 (size=262144)
I have a cluster with 90-95 web servers (8000-10000 ActiveConn,
50-60Mbs)
Neat!
It worked fine with 60 web servers. I added 30 servers and
changed the weigth. Now the weight is the speed of the cpu
but the problem is:
<side note>
Interesting idea. But this will lead to load imbalance since I don't
think you find processors with 750, 850, 933 and 1000 MHz which have the
same amount of L2 cache and FSB, which are the two crucial things when
it comes to request processing.
</side note>
starting lvs I have
[...]
FWM 15 wlc persistent 1200
-> web1.XXXXXXXXXXX:0 Route 1000 13 9
-> web2.XXXXXXXXXXX:0 Route 1000 119 286
-> web3.XXXXXXXXXXX:0 Route 933 123 179
-> web4.XXXXXXXXXXX:0 Route 933 126 218
-> web5.XXXXXXXXXXX:0 Route 933 115 240
-> web6.XXXXXXXXXXX:0 Route 933 118 376
-> web7.XXXXXXXXXXX:0 Route 750 95 166
-> web8.XXXXXXXXXXX:0 Route 850 109 75
-> web9:XXXXXXXXXXX:0 Route 850 105 255
[...]
[...]
after a moment I realize the weight changed (!?)
LVS doesn't change weight unless you use my threshold limitation patch
which you're obviously not using. This must be a third party software
interacting with ipvsadm.
[...]
FWM 15 wlc persistent 1200
-> web1.XXXXXXXXXXX:0 Route 100 13 9
-> web2.XXXXXXXXXXX:0 Route 1000 119 286
[...]
[...]
making stop/start I have the right weight.
What software are you using?
Cheers,
Roberto Nibali, ratz
|
