Draining for Maintenance
shannontuten
Member ✭
in System
Any suggestions on the best way to drain all connections from a server so that you can perform maintenance? In a non emergency situation I'd like to let active connections continue to a server but not to allow new connections. In time that would mean that the server would no longer have any connections and the end users would not have been disrupted in any manner.
Thanks for any tips.
Thanks for any tips.
0
Comments
I'll report back if it does indeed seem to be the piece I was missing.
Does that make any sense? If disabling a server works that way it would be fantastic. Otherwise it does appear that setting the priority and waiting (with the "scan all members" option selected) does seem to allow the server to drain. In my scenario I'm having to change that priority on several service groups, but if disabling the server doesn't act the same way I'm willing to take the extra steps.
Thanks for the info. If you can't answer I'll set up a test the first chance I get and see how it goes.
My thought is that if I know I need to patch a server but it isn't critical then I'll go change the priority and "come back later". This way all the clients will move to the other server(s) "naturally", if you will. I then disable the server for good measure and proceed with patching.
If I have an event that requires immediate attention, disable the server and wait a few minutes for everything to finish up and then proceed with whatever needs immediate attention.
If there is an event that falls in the middle of those two -- say I can't wait for the amount of time it takes to drain completely (or don't want to) then change priorities, wait as long as I can and then disable the server and proceed.
So far this seems to keep my outage completely behind the scenes from the masses.