<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Portal 10.6.1 HA Performance Issues in ArcGIS Enterprise Questions</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-questions/portal-10-6-1-ha-performance-issues/m-p/612183#M23521</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It would be great to get an haconfig.properties, nodes.properties, and portal-config.properties examples for a correctly configured ha portal env at 10.6.1.&amp;nbsp; I'm checking out all these files, noticing some strange things, and would like a baseline for what should be correct....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 07 Feb 2020 21:21:13 GMT</pubDate>
    <dc:creator>Jay_Gregory</dc:creator>
    <dc:date>2020-02-07T21:21:13Z</dc:date>
    <item>
      <title>Portal 10.6.1 HA Performance Issues</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/portal-10-6-1-ha-performance-issues/m-p/612182#M23520</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have configured two Portal machines as HA in my enterprise 10.6.1 deployment, and am getting some strange performance issues that I can't quite figure out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In short - requests through the web adapter (ie myportal.domain.org/gis/home) are taking an inordinately long time to resolve - sometimes 10 seconds or more (it was not like this before HA configuration).&amp;nbsp; Only if I directly make a request to the standby machine will anything resolve within an acceptable amount of time.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For the purposes of this, my base config is:&lt;/P&gt;&lt;P&gt;Machine A: Primary&lt;/P&gt;&lt;P&gt;Machine B: Secondary&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I bypass the web adapter and make a request to each individual machine (mymachine.domain.local:7443/arcgis/home) , making a request to the&amp;nbsp;Machine A (primary, so ostensibly the same machine the web adapter is making the request to) takes an equally long time.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, if I make a request to the Machine B (standby machine), it resolves quickly.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, if I stop the Portal for ArcGIS service on the Machine A, the Machine B gets promoted to primary.&amp;nbsp; Making a request to&amp;nbsp;machine B (previously standby machine but now primary) takes again, a very long time.&amp;nbsp; This means that it doesn't seem to be machine specific.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I restart the Portal for ArcGIS service on Machine A, Machine B remains as the primary, and Machine A is still standby, but now operational.&amp;nbsp; In this case, making a request to Machine A standby resolves quickly, where as Machine B primary does not resolve quickly.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In order to return to my base config from the beginning - I have to stop the Portal service on Machine B, which promotes Machine A to primary, and then restart Portal on Machine B (which keeps Machine A primary and Machine B standby).&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes, my head hurts to.&amp;nbsp; Any idea what could be causing this???&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Feb 2020 20:09:21 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/portal-10-6-1-ha-performance-issues/m-p/612182#M23520</guid>
      <dc:creator>Jay_Gregory</dc:creator>
      <dc:date>2020-02-07T20:09:21Z</dc:date>
    </item>
    <item>
      <title>Re: Portal 10.6.1 HA Performance Issues</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/portal-10-6-1-ha-performance-issues/m-p/612183#M23521</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It would be great to get an haconfig.properties, nodes.properties, and portal-config.properties examples for a correctly configured ha portal env at 10.6.1.&amp;nbsp; I'm checking out all these files, noticing some strange things, and would like a baseline for what should be correct....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Feb 2020 21:21:13 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/portal-10-6-1-ha-performance-issues/m-p/612183#M23521</guid>
      <dc:creator>Jay_Gregory</dc:creator>
      <dc:date>2020-02-07T21:21:13Z</dc:date>
    </item>
    <item>
      <title>Re: Portal 10.6.1 HA Performance Issues</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/portal-10-6-1-ha-performance-issues/m-p/612184#M23522</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If its a hardend environment check for certificate revocation&lt;/P&gt;&lt;P&gt;Particularly if your oganization makes it OWN SSL certs&lt;/P&gt;&lt;P&gt;I had a 30 second delay talking to Portal or AGS server sometimes&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;Always on first call from browser&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;All other calls went through quick after the first call times out.&lt;/P&gt;&lt;P&gt;It was tied to REVOCATION requests for certificates.&amp;nbsp; If the FIRE wall blocks the outside world you will get this behaviour from a user network talking to a harden backend.&lt;/P&gt;&lt;P&gt;ESRI has an article on revocation adjustments for MS Server and where to find it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Feb 2020 18:10:26 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/portal-10-6-1-ha-performance-issues/m-p/612184#M23522</guid>
      <dc:creator>WillStafford</dc:creator>
      <dc:date>2020-02-13T18:10:26Z</dc:date>
    </item>
  </channel>
</rss>

