Forum Discussion
Michael_Yates
Apr 26, 2011Nimbostratus
Given the scenario I think that your only option is to spread out the reboots over a longer period of time so that you can disable the server and prevent any new connections to the server (but considering the self-refreshing application you still run the risk of impacting your customers).
I think the application owner's design has lowered your number of available options, so they are going to have to help you mitigate the risk of customer impact.
My only suggestion is to insure that the "Action On Service Down" option on the Pool is set to "Reselect" so that when you do reboot the server the Customers are sent to a different server rather than just totally dropped.