To avoid user interruptions, and without manually re-configuring the web adaptor, can we remove one of the ArcGIS Server machines in our site while just that one machine is powered off?
Not sure if it is allowed/corrupts anything.
This one machine is being retired so we don't need to worry about it not being self-aware of its removal.
Reference:
https://enterprise.arcgis.com/en/server/10.7/deploy/windows/deleting-a-gis-server-from-a-site-in-manager.htm
Solved! Go to Solution.
Although unregistering an active machine from a site actually does two steps, stopping the machine and then unregistering it, I prefer to stop the machines first myself and then unregister them. Then if something goes wrong with stopping the machine, it won't potentially make for an unstable configuration.
In terms of stopping a machine, as soon as Server issues the command the web adaptors should stop sending requests to that machine. For requests that are active, Server and the web adaptors will wait until they complete before shutting down the service, and all the services need to be shut down before Server stops the machine. Depending on how many services are running and how long the requests takes, we can have machines take 15 minutes to fully stop.
A vast majority of the unavailable service errors we see in our logs are from machines starting up and not stopping.
Thinking that if the site does not restart the other ArcGIS Server in the process the users will not know anything happened.
Why can't you remove the machine from the site while it is still running and attached to the site? That is the cleanest way.
trying to avoid that one minute window of the web adaptor still sending requests to the machine before it auto - un- registers it (I think)
Although unregistering an active machine from a site actually does two steps, stopping the machine and then unregistering it, I prefer to stop the machines first myself and then unregister them. Then if something goes wrong with stopping the machine, it won't potentially make for an unstable configuration.
In terms of stopping a machine, as soon as Server issues the command the web adaptors should stop sending requests to that machine. For requests that are active, Server and the web adaptors will wait until they complete before shutting down the service, and all the services need to be shut down before Server stops the machine. Depending on how many services are running and how long the requests takes, we can have machines take 15 minutes to fully stop.
A vast majority of the unavailable service errors we see in our logs are from machines starting up and not stopping.