Rebuild Cache Options

Question

I'm looking for opinions/options for how to best rebuild cache on our production server services.  What I would like to do is rebuild the cache on a staging server and then copy the cache over to the production services.  I have a python script that will do this but it seems to be hit and miss on when it works.  The main hang-up on when it fails seems to be because it can't remove a .bundle file.

Does anyone know what causes a lock on a .bundle file?  As part of my script I stop the map service before copying over the cache.  Is this not enough?...does the entire ArcGIS Server service need to be stopped?

Is it better/more likely to not have any incidents if I just rebuild the cache on the production server?  The main reason I don't want to do this is to keep the computer resources available (CPU/RAM) on our production machine.  Rebuilding cache usually sucks up most of the available CPU and RAM which is why I am trying to rebuild the cache on a staging server then copy over.

Just wondering what others have tried and had success with.

Thanks in advance!!

MattMcGuire · Answer

The patch from March 30th is for BUG-000082467 not NIM104348. However, I gave it a try.

First, I tried to update an area of interest using Manage Map Server Cache Tiles. I Got the error, "Output failure, error string = Error moving bundle"

I installed this patch on both machines in a cluster (10.2.2)

I reran the Manage Map Server Cache Tiles. Low a behold, it worked.

So, I guess more testing is in order. If it was a fix, wouldn't they close NIM104348?

MikeVolz · Answer

This bug has been present since v10.2.2 and was not resolved with the v10.3 release.  Many AGS users have created incidents in regards to this bug.  The ESRI technical support specialist I spoke to about this bug says that ESRI development is working on the issue, but they have no idea when it will get resolved.  I am currently trying to create my AGS web apps so that I do not need to use cached services due to this very serious bug.

Update: ESRI released a potential patch for this bug in v10.2.2 today, 3/30/15.  The E-mail I received from ESRI says that a patch should be released soon for v10.3, so I would wait on this patch before continuing your cache update testing.

mpboyle · Answer

Perhaps I am...I don't know.  I should have mentioned the version...which is Server 10.3.  I guess I'm wondering when are locks placed on bundle files and how do you get rid of them?