Skip to main content

ArcGIS Server cluster naming issues

Permanently deleted user
I have been trying to configure one of our ArcGIS Server sites, which contains two servers in the cluster named 'default'.  We have a web adapter installed for this site and have disabled admin access to the site through the web adapter, for security reasons.

 

If I add a new ArcGIS Server in Analytics using the fully qualified domain name of the AGS web adapter (i.e. http://server.domain.name/arcgis/rest/services ), I have to use the pport 6080 address for the administrative settings URL.  This works fine, except for the fact that the server gets added to the list with the FQDN for both the cluster and the instance name.  This appears to be expected behaviour if the cluster name cannot be determined.

 

My question is why the cluster name cannot be determined when (see below) using the port 6080 URL for the REST endpoint allows it to find the cluster name properly.

 

Also, the second server is never listed even though both are listed through AGS Manager and admin REST endpoint.

 

If I use the port 6080 address for both the REST endpoint and administrative settings URL's , the server gets added to the existing 'DEFAULT' cluster (we have AGS installed on the same server as Analytics) with the FQDN of the server as the cluster.  Again, the second server in the cluster / site is never listed.  This seems to be a poor way of grouping servers - putting all servers with the same cluster name (ie. using the default 'DEFAULT' cluster name) together as a group.  Logically, I would want each cluster/site to be it's own group (as it is if I use the web adapter address for the services REST endpoint) but with the server names listed as the server instances).

 

Is there some reason why using the web adapter address for the services URL and the port 6080 URL for the administrative URL results in Analytics not being able to identify the cluster name and not seeing the second server in the cluster/site?

 

Peter.
0

Comments

4 comments

Date Votes
  • Permanently deleted user
    Hi Peter,

     

    It looks like there are two questions here.

     

    First, when you configure an ArcGIS Server with the web adapter URL and the (private) admin URL, it seems like the cluster information is not being correctly detected. This is a bug.  I'll get something filed for that, and we will address it in a future version :)

     

    As for your second question (the last paragraph), I'm sorry to say that this is a limitation of Analytics, and you will need to manually add the second server to get it to show up.  

     

    I hope this helps!

     

    Thanks,

     

    Danny
    0
  • Permanently deleted user
    Thanks for the reply, Danny.

     

    Please let me know what the bug tracking number is.  I have regular meetings with our account rep to follow up on the status of outstanding bugs affecting our business and want to add this to the list.

     

    I assume that even if Analytics were working properly, it would default to the behaviour identified in the last paragraph (server gets added to generic DEFAULT cluster grouping)?

     

    That being the case, I have a couple comments: 1) Is it not a bug also, that the second server (instance) in the cluster is not being picked up?  The user guide clearly states in section 2.3.8 that "Analytics only needs access to one of the servers within an ArcGIS cluster to ascertain the name of the cluster and display it and the other clustered servers correctly in the sidebar" 2) Given that ArcGIS Server 10.4+ defaults to single cluster mode (using the cluster name 'default') is it not poor design that multiple servers (could be from multiple environments - dev/test/staging/prod) would all show up under the 'default' cluster?

     

     
    0
  • Permanently deleted user
    Hi Peter,

     

    For sure, the tracking number is GID-1938.

     

    I don't think that is a separate bug, but rather a symptom of GID-1938.  If your cluster name is not being detected properly, then it won't be able to detect the other nodes in the cluster.  

     

    In regards to your second point, I think that's valid.  It would probably be better if we showed the site name and cluster name, as opposed to just the cluster name (or perhaps make it configurable in the settings).  I'll file that as well, and let you know the tracking number when it gets entered.  

     

    Thanks!

     

    Danny
    0
  • Permanently deleted user
    Hi Peter,

     

    The tracking number on the second request is GID-1939.

     

    Thanks!

     

    Danny
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post