I'd like to use Pound to load-balance across multiple backend servers.
The backend server applications have 'sticky' sessions, which the Group Session
Directive takes care of.
Is it possible to indicate to Pound that a backend service needs to be
gracefully removed? Ideally I could signal Pound in some manner and it would
dispatching existing sessions to the backend server, but would not allocate any
new sessions to that particular backend.
Admittedly this is only a problem because the sessions are sticky, but I think
it'll be difficult to rid the world of sticky sessions. And the concession
seems to have
been made already with the Session directive.
Looking through the mailing list archives I see that you frequently get
requests for having Pound reload it's configuration file. I was just about to
ask how to get
Pound to reload it's config...
I would have suggested adding a 0 priority and a mechanism to reload the config
file on the fly.
In one of those mails you suggest that Pound is simply stopped and started with
the new config.
Presumably this destroys any session-server affinity? Won't there be
situations where you need to change the configuration but not lose affinity?
Is there any other way to acheive this requirement?
Sign-up for Ads Free at Mail.com