|
Hi, Thomas
Thank you for your rapid reply !
> If it's not the case, please describe a bit more your configuration so
> we can help.
I'm sorry.... The following is the detail.
Please tell me advice !
- (1) network configuration
+-----------+
| traffic |
| generator |
+-----+-----+
|
-----------+-----+---------- 192.168.0.0/24
| .100
+----+----+
| LVS |
| host | <-- this one
+----+----+
| .100
-----------+-----+---------- 172.16.0.0/24
| .1 .2
+-----------+
| traffic |
| receiver|
+-----------+
- NAT mode
- traffic generator is web clients
- sending HTTP GET requests
- traffic receiver is real server
- (2) LVS host spec
hardware: CPU: Xeon 2.33GHz x 8(core)
^^^^^^^^^
MEM: 3Gbyte
software: Linux kernel: 2.6.18
ipvsadm : 1.24
keepalived : 1.1.15
- (3) keepalived configuration
virtual_server 192.168.0.100 80 {
delay_loop 3
lvs_sched wlc
lvs_method NAT
protocol TCP
virtualhost test
sorry_server 192.168.0.250 80
real_server 172.16.0.1 80 {
weight2
inhibit_on_failure
TCP_CHECK {
connect_port 80
connect_timeout 3
}
}
real_server 172.16.0.2 80 {
weight2
inhibit_on_failure
TCP_CHECK {
connect_port 80
connect_timeout 3
}
}
}
- (4) problem
When the CPS(new connections/sec) become over 15,000,
%CPU of ksoftirqd "jump" to 100% !!!
If it's just a max limit of hardware spec, I'll understand it.
But if we can improve the CPS much further, please tell me how to do.
--
Sincerely,
Mikio Kishi
On Mon, Nov 24, 2008 at 8:32 AM, Thomas Pedoussaut
<thomas@xxxxxxxxxxxxxx> wrote:
> Mikio Kishi wrote:
>> Hi, all
>>
>> Now, I'm doing the performance test of LVS with keepalived,
>> and facing with a problem like the following
>>
>> http://marc.info/?l=keepalived-devel&m=114040573028656&w=2
>>
>> But, I couldn't browse the solution.....
>> Please tell me the detail !
>>
>> Environment:
>> Linux kernel: 2.6.18
>> ipvsadm : 1.24
>> keepalived : 1.1.15
>>
> Let me guess, you are using LVS DR and have real servers running on the
> directors as well.
>
> The solution is to define your VIPs as FW marks rather than simple
> IP:port. In your iptable rule you can so exclude the packets originating
> from the other director (based on MAC) to be flagged with the right mark.
>
> If it's not the case, please describe a bit more your configuration so
> we can help.
> --
> Thomas
>
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://lists.graemef.net/mailman/listinfo/lvs-users
>
|
