[
https://issues.apache.org/jira/browse/YARN-5905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15675324#comment-15675324
]
Carlo Curino commented on YARN-5905:
------------------------------------
+1 pending yetus. It would be good to test this running in a live federation
cluster, before commit.
> Update the RM webapp host that is reported as part of Federation membership
> to current primary RM's IP
> ------------------------------------------------------------------------------------------------------
>
> Key: YARN-5905
> URL: https://issues.apache.org/jira/browse/YARN-5905
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: federation, resourcemanager
> Affects Versions: YARN-2915
> Reporter: Subru Krishnan
> Assignee: Subru Krishnan
> Priority: Minor
> Attachments: YARN-5905-YARN-2915-v1.patch, YARN-5905-v1.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
