[
https://issues.apache.org/jira/browse/TEZ-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15117747#comment-15117747
]
Sreenath Somarajapuram commented on TEZ-3073:
---------------------------------------------
[~cchepelov] Thank you for pointing this out.
- Will add a third host configuration to Tez UI 2 for the proxy.
- Also just to ascertain, is it correct to assume that all requests to RM's
REST APIs will still go to RMWebUrl?
Had a quick look into the patch, its good for POC.
- Please let me know if you would like me take it up.
- Or feel free to attach a patch for review when ready.
> 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)