Community
Select to view content in your preferred language

Upgrade from 11.3 to 11.4 broke shared instances

484
13
Jump to solution
a month ago
tcaulum_WPPI
by
Emerging Contributor
a month ago

I recently upgraded our environment from 11.3 to 11.4.  I keep up with latest releases as best I can, usually within a month or two. It's not a complicated setup so upgrades are straightforward.  This time, after what looked like a successful upgrade, most of our services were not accessible. 

I attempted the upgrade twice with the same result before realizing only the shared instances were not loading or accessible via REST.  I searched for any reason at all why this is happening but found nothing.  On a whim, I changed the settings for our shared instances from 8 shared instances per machine to 4.  For some reason this fixed it.  I even changed it back to 8 and everything is working fine.  

tcaulum_WPPI_0-1732895276273.png

 

Just wanted to make a post in case anyone else found this same issue. 

13 Replies
JoySoulliere
by
Emerging Contributor
a week ago

Thank you so much.  I also had this issue and stopping and starting the DynamicMappingHost fixed the issue. 

DenisLalonde
by
Occasional Contributor
a week ago

A bit more info that seems to have solved the issue on my end when rebooting our server:

- Set ArcGIS Datastore, Portal, Server services to manual

- In Scheduled Tasks on system startup, via a .bat file, stagger the ArcGIS component startup leaving a full 10 minutes for Portal to start before starting the ArcGIS Server service.

- In my case, after system starts up, wait 5 minutes, then start Datastore, wait 5 minutes, then start Portal, wait 10 minutes, then start Server

- I have always had a 5-minute stagger between each, but after the upgrade to 11.4, it looks like Portal needs more time than that now

- This issue was logged as a defect and is being reviewed by ESRI product teams.

tcaulum_WPPI
by
Emerging Contributor
8 hours ago

I'll test this as well, this would be easier to automate than my solution.  Let me know if a permanent solution arises.  It's starting to feel like something that won't have a fix until 11.4.1 unless its widespread enough to make a separate patch.  I'll open up a bug report for it.

0 Kudos
DavidColey
by
Honored Contributor
Friday

Yeah, I had some wankiness on this as well, but not until we performed our restarts as part of the Windows Updates and then restarts.  We too always restart in a stagger, with our config server going first, then host site server 1, host site server 2, relational data store, object store, fed site server 1, fed site server 2, and then portal server.

So being aware of the Dynamic Mapping host service not behaving, I wasn't sure how that was going to manifest on our system.  For the host site, it's not a big deal as we only use the host site for hosted feature layers, vectortile layers, scene layers...

For the Federated site, it does matter.  That's the site, (for us) hosting referenced feature access services in shared instances. After our restarts, I could see the dynamic mapping host was running on federated server 1, but was not running on federated server 2.  

After I restarted federeated server 2, dynamic mapping host came back up and so was visible as running on both machines.  Then I went in to site settings, decreased to 4, saved.  Then increased back to 8 (per machine) saved again.  Then for server manager for the federated site, I restarted the dynamic mapping host service.  It came back up showing 16 available max instances.

So that did it for us, but I will be checking it's status after next months windows updates / server restarts