Alex Hunsley wrote:
So I was wondering if anyone has worked out a way to get around the
fairly abrupt nature of config reloads in Pound?
One way to retain all the current sessions when you restart pound:
1) Drain all the connections from all but one of the backends
2) Wait for all of the sessions attached to other backends to expire
3) Restart pound, and immediately make the same backends inactive again
4) Wait for the session timeout period - all the active sessions are
forced to re-establish themselves with the original server, because it's
the only one active (any sessions that are not re-established within
this period are invalid anyway)
5) Re-activate the rest of the backends
It's not ideal, but it works. It'd be better if pound could simply dump
its current sessions to disk, and attempt to reload them (assuming the
config fiule hadn't changed significantly in the meantime) on startup.
Regards,
Russ