Peter van Dijk wrote:
[snip][...]
Just another vote for this feature. Both a & b would be great, but a)
would be most helpful to us.
I need to add a new host today and it would be great not to have to
close the site. I also needed to change the pem file a while back, and
that's a similar deal.
Maybe retain any existing session mappings regardless of the
config changes. That way if the admin wants to remove a machine
they can let those sessions bleed off until it's safe to remove
from the pool.
And if it's running chroot and can't read the config file, then
graceful restarts just aren't available.
Maurice
Re: buffering; runtime reloading and/or state saving Nicholas Avenell <nicholas(at)evolvingmedia.co.uk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Maurice Aubrey wrote:[...][...][...]
And another vote from here.
- --
Nicholas Avenell
Technical Developer[...]
Re: buffering; runtime reloading and/or state saving Chris Wilson <chris(at)aidworld.org>
Hi all,
[...]
cluster,[...]
(and[...]
thing[...]
problem[...]
a)[...]
I hate to say it, but Me Too(TM) :-)
We have to run another load balancer behind Pound to allow us to
reconfigure our server pool without user visible downtime. Of course
that means that we can't use Pound's session tracking at all :-(
Cheers, Chris.[...]