Sticky-purge

[abenanti]

Hi

We implemented about 50 contents rule on our css all of them are productive. each time when we put a new application we make several performance-test with up to 500 user.

We start always only with one server after that we enable the second server.

To have loadbalancig we must purge the sticky database otherwise all the user connects to the first server. The problem is all the server are connected to the css through a catalyst6500 by a trunk. When we purge the database we only can do this per interface. That means all connected user (Productive) have to log in again because the https breaks! Does anybody know what I can do?

cheers

andrea

[Gilles Dufour]

I would say, configure the sticky inactive timeout to 5 minutes (or whatever you think is best) and then wait 3 times this amount of time.

This should clear all the sticky entries that are inactive.

Then remove the timeout.

Not tested, but this is the only option you have I believe.

Gilles.