[
https://issues.apache.org/jira/browse/YARN-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13935329#comment-13935329
]
Robert Kanter commented on YARN-1811:
-------------------------------------
Ok, I'll make it {{@Public}} and put back the old constants and behavior. The
AmIpFilter is supposed to be created by the AmFilterInititalizer, so I think we
can make the new constants package private so that only the Inititalizer uses
them going forward; and mark the old constants as deprecated.
I agree that it would be simpler to just redirect to any of the RMs and assume
it auto-redirects to the active RM. Though this won't work if that RM is
currently down; so I think we have to check for the active RM, which should be
up. I'll look at RMHAUtils though.
{{conf.getValByRegex()}} seemed simpler, but I see your point. If they have
some invalid config properties that match, it will pick those up.
> RM HA: AM link broken if the AM is on nodes other than RM
> ---------------------------------------------------------
>
> Key: YARN-1811
> URL: https://issues.apache.org/jira/browse/YARN-1811
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Affects Versions: 2.3.0
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Attachments: YARN-1811.patch, YARN-1811.patch, YARN-1811.patch,
> YARN-1811.patch
>
>
> When using RM HA, if you click on the "Application Master" link in the RM web
> UI while the job is running, you get an Error 500:
--
This message was sent by Atlassian JIRA
(v6.2#6252)
