BUG-000153780 for ArcGIS GIS Server

Numéro d’ID de bogue	BUG-000153780
Envoi	November 17, 2022
Dernière modification	June 5, 2024
S’applique à	ArcGIS GIS Server
Version trouvée	10.9.1
Système d’exploitation	N/A
Version du système d’exploitation	N/A
Statut	Known Limit

Informations supplémentaires

This is a known issue. It is because it has multiple server nodes with multiple instances. Some instances are refreshed, while others are not. When you send a refresh service call, the corresponding image service is not refreshed automatically. Instead, it generates a flag for the image service. The next call to the image service destroys the existing instance and creates a new one to pick up new data in the mosaic dataset. However, this might conflict with another server functionality. By default, the server system cleans up the folder that stores the refresh flag file when it reaches 10 minutes old. So, if the new image service call is received after 10 minutes of the image service refresh, the refresh is not going to take effect. This does not mean the refresh service call has failed, as noticed. It is just the flag that is deleted without affecting anything.

Solution de contournement

A few settings to try:

Make the 'keep alive interval' property of the image service less than the ArcGIS output folder 'max file age' (https://server/arcgis/admin/system/directories/arcgisoutput). In this way, bad instances are killed before the flag file (which is stored in the ArcGIS output folder) is deleted.
Send some dummy image server calls at the same time right after the image service refresh flag is generated. This is to make sure all instances are hit and refreshed.