The problem is not LVS. The problem is in your Apache Benchmark
computer. When you suddenly stop one of the server, lvsipadm
can not redirect the traffic right away. So the TCP wait state takes
so many possible connections out from your ab computer and
it had to stop until the TCP wait state number drops.
At 10:27 PM 8/1/00 +0800, Tim Wu wrote:
>Dear All,
>
> I found a strange problem and I can't sure it is a bug of LVS.
>My LVS testbed includes a LVS dispatcher, three web realservers,
>and a client running ab(Apache benchmark). LVS is setup in nat mode.
>Lan bandwith is 100Mbit.
>
>If I add or remove realserver with ipvsadm while ab is sending
>http requests to LVS in very high speed(about 500 req/s), the LVS
>will stop dispatching any connection until I let it take a rest
>by stoping ab (wait the inactive connection become 0).
>
>Anyone has the same experience on this?
>
>
|