Sign in
Categories
Your Saved List Become a Channel Partner Sell in AWS Marketplace Amazon Web Services Home Help

Esri ArcGIS 10.4.1 for Server on Ubuntu with Postgresql (Dec 2018)

Esri | 10.4.1 (Patched Dec 2018)

Linux/Unix, Ubuntu 14.04 LST - 64-bit Amazon Machine Image (AMI)

Reviews from AWS Marketplace

1 AWS reviews
  • 5 star
    0
  • 4 star
    0
  • 1
  • 2 star
    0
  • 1 star
    0

External reviews

471 reviews
from G2

External reviews are not included in the AWS star rating for the product.


3-star reviews ( Show all reviews )

    Paul

AGS Geoprocessing Services in a site are problematic

  • September 02, 2016
  • Review verified by AWS Marketplace

Architecture of AGS services in AWS sometimes appears a dark art. However I would say the availability of both AGS for Linux and Amazon EFS would lead many naturally towards a site architecture with AGS site config and directories on EFS then NFS mounted to these Ubuntu AMIs. At least that seems very reasonable to me. Setting up a site in this manner with typical map services seems to work okay. Administration tasks are not speedy but that is not a deal breaker. The resulting services perform as expected. The problem occurs with geoprocessing services. For unclear reasons AGS for Linux experiences an extreme performance hit when executing gp services in EFS or NFS hosted job directories (reference case #01822810). A simple buffer gp process that executes in a few seconds on a stand-alone machine takes over a minute with a site sharing directories via EFS. As far as solutions go by far the easiest is to just don't do this. Host your gp services on single machine sites with directories on the local EBS volumes. Then all works fine. Another partial solution is to alter your GP services via the rest admin to utilize a local EBS directory as the service job directory. This solves the performance problem but breaks the service overall as you can only query that specific machine for the jobs results. If your load balancer or web adapter routes your request to one of the other machines you will just get a strange error. Another partial approach I tried was to place the gp service machine in its own cluster. This brings up another issue in that clustering entirely does not seem work in this scenario. I assume clustering requires some speedy writes to the common config location and without that it just locks up. So just putting this out there to perhaps save other folks some aggravation. Esri declines to support this issue so I would very much be interested if you have any advice or experience to share. Cheers, Paul


showing 1 - 1