[
https://issues.apache.org/jira/browse/TEZ-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15118980#comment-15118980
]
Cyrille Chépélov commented on TEZ-3073:
---------------------------------------
Thanks [~Sreenath]. Yes, RM REST APIs got to RMWebUrl, but webproxy calls go to
the "new" RMProxyUrl. All three services must have the TEZ-UI origin
greenlighted in their CORS setup (which for RM requires having [YARN-4009] in).
For now, we're fine using tez-ui-0.8.2 as patched here. Looking forwards to
trying out Tez UI 2 in time, but no hurry for us. I guess it'll be more
efficient if you take care of this when it makes sense to do so. Thanks a lot!
> Support for separate WebProxy
> -----------------------------
>
> Key: TEZ-3073
> URL: https://issues.apache.org/jira/browse/TEZ-3073
> Project: Apache Tez
> Issue Type: Improvement
> Components: UI
> Affects Versions: 0.6.2, 0.8.2
> Environment: YARN 2.6.0
> Reporter: Cyrille Chépélov
> Priority: Minor
> Labels: patch
> Attachments: tez-ui_configs.js, tez-ui_main.js.diff
>
>
> When running the YARN WebProxy separate from the YARN ResourceManager (as
> suggested by the YARN Documentation on security grounds), some REST calls
> should no longer be made to RMWebUrl but to the proxy instead.
> Attached here is a Proof of Concept patch which works against tez-ui-0.8.2,
> which would need to be refreshed with TEZ-UI 2
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
