Currently when RM HA is enabled, the webapp host is randomly picked from one of the ensemble RMs and relies on redirect to pick the active primary RM. This has a few shortcomings:
- There's an overhead of additional network hop.
- Sometimes the rmId selected might be an instance which is inactive/decommissioned
- In few of our clusters, we have redirects disabled (either in client or server side) and then the invocation fails.
This JIRA proposes updating the RM webapp host that is reported as part of Federation membership to the current primary RM's IP.