[
https://issues.apache.org/jira/browse/YARN-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Zampino updated YARN-8125:
-------------------------------
Description:
If the YARN UI is accessed via the standby resource manager endpoint, it
automatically redirects the requests to the active resource manager endpoint.
YARNUIV2 should behave the same way.
Apache Knox 1.0.0 introduced the ability to dynamically determine proxied
RESOURCEMANAGER and YARNUI service endpoints based on YARN configuration from
Ambari. This functionality works for RM and YARNUI because even though the YARN
config may reference the standby RM endpoint, requests are automatically
redirected to the active endpoint.
RM and YARNUI requests to the standby endpoint result in a HTTP 307 response.
YARNUIV2 should respond similarly.
If YARNUIV2 behaves differently, then Knox will not be able to support its own
dynamic configuration behavior when proxying YARNUIV2.
KNOX-1212 adds the integration with Knox, but KNOX-1236 is blocked by this
issue.
was:
If the YARN UI is accessed via the standby resource manager endpoint, it
automatically redirects the requests to the active resource manager endpoint.
YARNUIV2 should behave the same way.
Apache Knox 1.0.0 introduced the ability to dynamically determine proxied
RESOURCEMANAGER and YARNUI service endpoints based on YARN configuration from
Ambari. This functionality works for RM and YARNUI because even though the YARN
config may reference the standby RM endpoint, requests are automatically
redirected to the active endpoint.
If YARNUIV2 behaves differently, then Knox will not be able to support its own
dynamic configuration behavior when proxying YARNUIV2.
KNOX-1212 adds the integration with Knox, but KNOX-1236 is blocked by this
issue.
> YARNUIV2 does not failover from standby to active endpoint like previous YARN
> UI
> --------------------------------------------------------------------------------
>
> Key: YARN-8125
> URL: https://issues.apache.org/jira/browse/YARN-8125
> Project: Hadoop YARN
> Issue Type: Bug
> Components: yarn-ui-v2
> Reporter: Phil Zampino
> Priority: Major
>
> If the YARN UI is accessed via the standby resource manager endpoint, it
> automatically redirects the requests to the active resource manager endpoint.
> YARNUIV2 should behave the same way.
> Apache Knox 1.0.0 introduced the ability to dynamically determine proxied
> RESOURCEMANAGER and YARNUI service endpoints based on YARN configuration from
> Ambari. This functionality works for RM and YARNUI because even though the
> YARN config may reference the standby RM endpoint, requests are automatically
> redirected to the active endpoint.
> RM and YARNUI requests to the standby endpoint result in a HTTP 307 response.
> YARNUIV2 should respond similarly.
> If YARNUIV2 behaves differently, then Knox will not be able to support its
> own dynamic configuration behavior when proxying YARNUIV2.
> KNOX-1212 adds the integration with Knox, but KNOX-1236 is blocked by this
> issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
