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.
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). Only if I directly make a request to the standby machine will anything resolve within an acceptable amount of time.
For the purposes of this, my base config is:
Machine A: Primary
Machine B: Secondary
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 Machine A (primary, so ostensibly the same machine the web adapter is making the request to) takes an equally long time.
However, if I make a request to the Machine B (standby machine), it resolves quickly.
Now, if I stop the Portal for ArcGIS service on the Machine A, the Machine B gets promoted to primary. Making a request to machine B (previously standby machine but now primary) takes again, a very long time. This means that it doesn't seem to be machine specific.
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. In this case, making a request to Machine A standby resolves quickly, where as Machine B primary does not resolve quickly.
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).
Yes, my head hurts to. Any idea what could be causing this???
