So new connections would be sent to the other server(s). When you say “established connections continue to completion”, you mean in flight conversations? I’m wanting to go a step further and let any persistence to continue to send an existing client to that server. This way it will reduce any chance of the end user noticing the server going down. An example would be two web servers that don’t persist session state to a central location. The user would continue to get their session state until they would normally be idled off the server. If they reconnected it would be to the new server.
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.