Select to view content in your preferred language

ArcGIS Ent Azure Native multi node service issues (site sync and deleting services)

164
0
Sunday
Labels (1)
FraserHand
Frequent Contributor

Hi there,

I am seeing a strange issue with multi node ArcGIS Server sites in both 12.0 and 12.1 using the Azure cloud native pattern.

Test environment is vanilla Azure (no landing zones or Management groups / policies) using ArcGIS Enterprise Cloud Builder 12.0 for Azure to create a 12.0 deployment do some testing then upgrade to 12.1. The environment is:

  • Two server deployment with full base deployment
  • Using the Esri CB server images (Windows Server 2025 Datacenter)
  • ArcGIS Server is deployed to Cosmos DB, Service Bus and a blob container in a Storage account (V2)
  • Portal for ArcGIS is using blob storage for content
  • All artefacts deployed via Cloud Builder
  • Upgrade to 12.1 run after first lot of testing on both servers.

What I see is this

Full config store is in Cosmos DB as expected

Both servers have a c:\arcgisserver\ local directory with \directories (arcgissystem etc.) \local and \logs (no additional data drives)

The first server has a .site folder in the C:\arcgisserver\directories\arcgissystem with the site DAT, the second server does not have this folder (I do not know if this is expected)

FraserHand_0-1779659218602.png

When publishing to the server the service is published correctly to both nodes in the site and the ArcSOC processes come up for dedicated services.

FraserHand_1-1779660550810.png

When deleting a service, it isn't removed from the one of the nodes

FraserHand_2-1779660726202.png

 

FraserHand_3-1779660832437.png

Full service definition is still in the local directory

FraserHand_4-1779660875270.png

Same behaviour when deleting another service

FraserHand_5-1779660929086.png

FraserHand_8-1779660995358.png

When looking in cosmos db the service definition is still present

FraserHand_9-1779661162260.png

Note the content elements is null but the cosmos db entry is still there.

Server logs describe the service being removed

FraserHand_10-1779661263989.png

No SEVERE or WARNING log entries to indicate the service deletion failed.

This causes issues when services are republished as one of the nodes now has a stale service definition. We have seen issues where a service with updated symbology from associated font files returns missing symbols as the App Gateway load balances between the server nodes and the  second node where the service wasn't deleted returns the old service definition.

Note at 12.0 we have seen issues with publishing where services are NOT present on both nodes and the c:\arcgisserver\directories\arcgissystem\arcgisinput directory is different between the 2 ArcGIS Server nodes.

FraserHand_0-1779661845343.png

In this example node 2 was missing the entire Utilities folder and SampleworldCities as an example.

Has anyone come across this behaviour at 12.0 / 12.1? Currently our workaround is to remove the second node from the site. These have been added to support sites that require high throughput.

Thanks!

EDIT: Also note that performing a synchroniseWithSite operation on the second node does not remove the deleted service definitions / folders.

 

EDIT: When deleting a service via manager I can see the service only being deleted on one node:

FraserHand_0-1779669221491.png

 

EDIT: I have been doing a bitt of further testing and even though the service folders are left behind, a subsequent publish does appear to update them at 12.1 - I am confirming this against 12.0. It seems to be inconsistent as to with node actually has the service deleted.

EDIT: From a 12.0 multi node site when a service is deleted the service folder in \arcgisinput is usually left on the second node (fully deleted from node 1). If I republish the service *sometimes* the folder is deleted and replaced with the updated service and sometimes it isn't, leading to a mismatch service definition on node 1 and node 2. If this happens you have to delete the service then manually delete the left over folder from the second node before republishing.

 

 

 

0 Kudos
0 Replies