Okay, I've found documentation.
Thanks so much for letting me know about this. On 30.01.2016 13:07, weirdfish+subs wrote: > Really? Excellent. > > Does that allow you to mark a back end to accept no new connections, so that those currently connected can finish, and disconnect, and then you can take the back end server offline without killing sessions off? > > Can you point me in the direction of documentation examples of poundctl please? > > Err-config - yes, thanks - I know about that - it was less whether they can be configured, but more can you wind down the back end connections without restarting Pound, so that you don't have to kill active sessions. > > On 30.01.2016 09:37, qutic development wrote: > >> Think pound can already do things on your wish list. >> >>> Ability to set properties dynamically to run down connections to individual back ends / full services / entire Pound. This would help taking nodes out of load balance, for example, for maintenance. >> >> You can deactivate backends with poundctl and bring them back later. >> >>> Keeping Pound online whilst doing this could allow it to present a default "If you are seeing this page, the service you are looking for is undergoing maintenance" kind of thing. This'd be really useful in my 24/7 environment, where my back ends don't have graceful wind down of connections. >> >> Pound has several Err-Config directives for that, like: >> >> Err500 "/var/www/pound/500.html" >> Err503 "/var/www/pound/503.html" >> >> -- >> To unsubscribe send an email with subject unsubscribe to [email protected]. >> Please contact [email protected] for questions.
