()ý
Home
Ȩ ȸҰ ý Ʈ ũ
 
 
ۼ : 06-07-27 18:48
foundry weighted .
 ۾ :
ȸ : 3,107  

telnet@readysystem(config)#
telnet@readysystem(config)#server real web1 192.168.0.24
telnet@readysystem(config-rs-web1)#port http
telnet@readysystem(config-rs-web1)#exit
telnet@readysystem(config)#server real web2 192.168.0.212
telnet@readysystem(config-rs-web2)#port http
telnet@readysystem(config-rs-web1)#port http keepalive
telnet@readysystem(config-rs-web1)#exit
telnet@readysystem(config)#server real web2
telnet@readysystem(config-rs-web2)#port http keepalive
telnet@readysystem(config-rs-web2)#exit
telnet@readysystem(config-rs-web2)#server virtual v1 192.168.0.90
telnet@readysystem(config)#
telnet@readysystem(config)#server virtual v1
telnet@readysystem(config-vs-v1)#port http
telnet@readysystem(config-vs-v1)#bind http web1 http
telnet@readysystem(config-vs-v1)#bind http web2 http
telnet@readysystem(config-vs-v1)#exit
telnet@readysystem(config)#server predictor round-robin
telnet@readysystem(config)#server real web1
telnet@readysystem(config-rs-web1)#weight 7
telnet@readysystem(config-rs-web1)#exit
telnet@readysystem(config)#server real web2
telnet@readysystem(config-rs-web2)#weight 2
telnet@readysystem(config-rs-web2)#exit
telnet@readysystem(config)#server predictor weighted

 ̷ ϰ ش Ǹ Ͽ Ȯ غ .....


 web1 ---- weighted : 7 
 web2 ---- weighted : 2


󿡼 web1 ټ web2 ѹ ϴ.


 


Comparison of Connection Assignments


The following tables illustrate the difference in how connections are assigned to servers when the weighted predictor is configured, compared to the enhanced weighted predictor. Assume a configuration with three real servers, A, B, and C. Real server A has a weight of 1, real server B has a weight of 2, and real server C has a weight of 3. The numbers in bold indicate which server receives the new connection.


When the weighted predictor is configured, connections are assigned as follows:































































































































Table 3.3: SLB with the weighted predictor

Real Server A

Real Server B

Real Server C

weight = 1

weight = 2

weight = 3

Connections

Server Load1

Connections

Server Load

Connections

Server Load


0



0 / 1 = 0



0



0 / 2 = 0



0



0 / 3 = 0



0



0 / 1 = 0



0



0 / 2 = 0



1



1 / 3 = 0



0



0 / 1 = 0



0



0 / 2 = 0



2



2 / 3 = 0



0



0 / 1 = 0



0



0 / 2 = 0



3



3 / 3 = 1



0



0 / 1 = 0



1



1 / 2 = 0



3



3 / 3 = 1



0



0 / 1 = 0



2



2 / 2 = 1



3



3 / 3 = 1



1



1 / 1 = 1



2



2 / 2 = 1



3



3 / 3 = 1



1



1 / 1 = 1



2



2 / 2 = 1



4



4 / 3 = 1



1



1 / 1 = 1



2



2 / 2 = 1



5



5 / 3 = 1



1



1 / 1 = 1



2



2 / 2 = 1



6



6 / 3 = 2



1



1 / 1 = 1



3



3 / 2 = 1



6



6 / 3 = 2



1



1 / 1 = 1



4



4 / 2 = 2



6



6 / 3 = 2



2



2 / 1 = 2



4



4 / 2 = 2



6



6 / 3 = 2



2



2 / 1 = 2



4



4 / 2 = 2



7



7 / 3 = 2



2



2 / 1 = 2



4



4 / 2 = 2



8



8 / 3 = 2






1For the weighted predictor, the server load is calculated as
connections / server weight = server load. Fractional remainders are rounded down. If there is a tie, the server with the highest weight receives the connection.



When the enhanced weighted predictor is configured, connections are assigned as indicated in the following table.































































































































Table 3.4: SLB with the Enhanced Weighted predictor

Real Server A

Real Server B

Real Server C

weight = 1

weight = 2

weight = 3

Connections

Server Load1

Connections

Server Load

Connections

Server Load


0



0 x 6 / 1 = 0



0



0 x 6 / 2 = 0



0



0 x 6 / 3 = 0



0



0 x 6 / 1 = 0



0



0 x 6 / 2 = 0



1



1 x 6 / 3 = 2



0



0 x 6 / 1 = 0



1



1 x 6 / 2 = 3



1



1 x 6 / 3 = 2



1



1 x 6 / 1 = 6



1



1 x 6 / 2 = 3



1



1 x 6 / 3 = 2



1



1 x 6 / 1 = 6



1



1 x 6 / 2 = 3



2



2 x 6 / 3 = 4



1



1 x 6 / 1 = 6



2



2 x 6 / 2 = 6



2



2 x 6 / 3 = 4



1



1 x 6 / 1 = 6



2



2 x 6 / 2 = 6



3



3 x 6 / 3 = 6



1



1 x 6 / 1 = 6



2



2 x 6 / 2 = 6



4



4 x 6 / 3 = 8



1



1 x 6 / 1 = 6



3



3 x 6 / 2 = 9



4



4 x 6 / 3 = 8



2



2 x 6 / 1 = 12



3



3 x 6 / 2 = 9



4



4 x 6 / 3 = 8



2



2 x 6 / 1 = 12



3



3 x 6 / 2 = 9



5



5 x 6 / 3 = 10



2



2 x 6 / 1 = 12



4



4 x 6 / 2 = 12



5



5 x 6 / 3 = 10



2



2 x 6 / 1 = 12



4



4 x 6 / 2 = 12



6



6 x 6 / 3 = 12



2



2 x 6 / 1 = 12



4



4 x 6 / 2 = 12



7



7 x 6 / 3 = 14



2



2 x 6 / 1 = 12



5



5 x 6 / 2 = 15



7



7 x 6 / 3 = 14






1For the enhanced weighted predictor, the server load is calculated as
connections x [combined weights / server weight] = server load. Fractional remainders are rounded down. If there is a tie, the server with the highest weight receives the connection.


 
 

Total 136
ȣ     ۾ ¥ ȸ
46 veritas volume manager
2006/10/09 3581
45
2006/10/02 3247
44 apache httpd.conf
2006/09/25 7395
43 sendmail
2006/09/13 6527
42 (DNS) ȯ 
2006/09/13 5304
41 NOQUEUE: SYSERR(root): /etc/mail/sendmail.cf: line 483:
2006/08/31 4653
40 sendmail --dangerous permissions=40777 ERROR
2006/08/31 6131
39 snedmail - db DNEWdb , DNdbM ,DNIS, -DNISPLUS , DMAP_REGEX
2006/08/31 3495
38 foundry load balancing .
2006/07/28 6224
37 foundry weighted .
2006/07/27 3108
36 foundry SLB
2006/07/27 11021
35 foundry Ʈ
2006/07/27 3024
34 foundry Web Management interface login dialog
2006/07/27 5970
33 foundry load balancing
2006/07/26 4515
32 L4 ϴ Ϻл ˰
2006/07/26 9587
 1  2  3  4  5  6  7  8  9  10  
 
 
 
Administrator Login