Hello all,

Since a few days we are using Pound as loadbalancer in front of three
backends running a session oriented web-application. I am using IP based
session tracking (the COOKIE version for me appears unreliable, I regularly
get dropped sessions, but IP is not a problem). It works like a charm and is
a great relief from Apache...

I browsed the archives and saw there has already been some discussion on
this topic. I would like to know the status on this since it is crucial to
me to be able to take the backends out of service one by one, update the
software, restart them and put them back in the pool.

Obviously, taking a backend out of service does not mean killing it directly
but just not assigning new sessions to it so it will go idle by itself. Part
of our system is an internet-survey-based market-research tool so there are
many users almost around the clock that stay around for a few minutes up to
about 30-45 minutes).

Changing the config and doing "force-reload" seems to simply restart the
server and drop all current sessions which is unacceptable.

Is there already a way to do this? If not, will support for such a thing
become available?

Regards,

Silvio Bierman