Community
Select to view content in your preferred language

The MigrateSceneServices command line tool should provide the time required to migrate a scene layer

139
1
2 weeks ago
Status: Open
kntr
by
Regular Contributor

Currently in 11.4, the new MigrateSceneServices tool can be used to migrate scene services from the Tile Cache Data Store to the Object Store in bulk.

However, we have a lot of 3D contents (scene layers) and some are very large in size. Is it difficult to estimate downtime needed for our systems to upgrade from a previous version of Enterprise to 11.4.

It would be best if there is logs on the time taken to migrate a scene layer. So we can test migrating in our non-production environment and estimate the downtime in our production environment.

Reference: https://enterprise.arcgis.com/en/server/latest/publish-services/linux/migrate-scene-services-utility...

1 Comment
smalipeddi
by
2 weeks ago

Hi

Thank you for the post. It is a good idea to show the time it takes to migrate a service, but it won’t be accurate as the cache typically have millions of objects and some are very small objects, and some are large objects with textures etc. The time to transfer these files vary and therefore it is hard to estimate time correctly. We do show the percent completion and that would give you rough estimates. Having said that, we will consider it if we get deterministic time estimates as we progress the migration process.

You did mention your concern with the down time with the migration. There will not be any down time with the migration. The services continue to work while the migration is in progress. At the end of the successful migration, there will be a split-second down time to switch the cache to point to the new migrated cache in objects store. If there are any failures with the migration process, we do not point to the new cache, so you are safe. I thought I let you know this if you are not aware of it.

Also, you mentioned that you have some very large caches. Here is a tip. Before you migrate large caches, ensure the heap-size set on your object store is adequate as the migration process is memory intensive operation. Here is what you can do before migrating large scene caches:

  1. Use the DescribeDatastore tool and examine the current heap-size set on the object store. When you install the software, we calculate the correct heap size based on your hardware resources. The only exception to this is when you install your software on a single machine with Enterprise Builder setup. In this case we set the minimum 1 GB heap size. This is typically not sufficient when you migrate large scene caches.
  2. If necessary, use the Changedbproperties tool to increase the heap-size. See documentation on how we calculate it.
    Note: This is true while migrating old scene caches and while creating new large caches that write to object store.

Hope these tips would help you in successful migration of your scene caches to the object store.

Satish