I want to publish a Geoprocessing service to multiple (cloud/cluster) ArcGIS server instances (for high availability) but I'm not sure how to share jobs. I.E. Lets say I have just one async GP service that I have published to an instance (gold instance) in a cloud provider and create an image of that instance. That means I can spin up multiple identical instances. If an instance becomes unhealthy and terminates - no problem as other instances are there to handle new processing jobs. However, if I submit a job to this cluster - it will land on one instance and the JOB ID will only exist on that one instance -other instances won't know about that JOB ID. I'm prepared to lose any jobs that may be running on an unhealthy instance but I don't want to lose incoming jobs as we wait for a replacement instance to spin up. I suppose I could run a hot-spare type setup. There must be a better way though?
... View more
