|
In my experience, I've had to remove the real server entirely when I
have persistence active. Unless of course you're willing to wait an
hour :). But I also have had new connections continue to trickle in
to a zero-weight real server in the absence of persistence, so I
think there's also a general issue where a zero weight isn't
literally zero.
I remove real servers within health monitoring in the general case,
as opposed to zero-weighting them. If zero worked as expected, that
slightly drastic measure (hard connection interruptions, orphans)
wouldn't be necessary.
Good luck,
--
Ken.
On Jun 13, 2006, at 6:13 AM, Hildebrand, Nils, 122 wrote:
Hi,
I subscribed to the mailing list, because I had a major problem
with ipvsadm
today.
I am using ipvsadm v1.24 on a SuSE 9.3 professional (Kernel
2.6.11.4-21.11-smp).
For configuring lvs I use lvs-kiss.
I am doing a load-balancing for two webservers.
Now the problem:
The service is configured with a persistency of one hour.
After some clients connected through lvs to Webserver #2 the
Webserver #2
went down.
Some seconds later lvs-kiss realized the servers was down and set
the weight
for that server to zero.
BUT: Clients were still trying to connect to Webserver #2.
After I looked at "ipvsadm -Lc" I found that their old connection
was still
there and the timeout-value for Webserver#2 got reset to one hour
againg
after every try.
I would have expected that all Webserver #2-connections will get
invalidated
and that the client-retry would then go to Webserver #1.
What's wrong here?
BTW: Is there any way to zero the connection-table?
ipvsadm -Zc oder -Cc does not work...
Kind regards, Nils
_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://www.in-addr.de/mailman/listinfo/lvs-users
|
