[jira] [Comment Edited] (YARN-5145) [YARN-3368] Move new YARN UI configuration to HADOOP_CONF_DIR
[
https://issues.apache.org/jira/browse/YARN-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576368#comment-15576368
]
Sreenath Somarajapuram edited comment on YARN-5145 at 10/14/16 8:16 PM:
- Minor comment, Ember Logger could be used instead of direct console log.
- Looking at {code}if(address == "0.0.0.0") {{code}, just wondering if we could
have condition where the addres comes as localhost or 127.0.0.1
was (Author: sreenath):
- Minor comment, Ember Logger could be used instead of direct console.
- Looking at {code}if(address == "0.0.0.0") {{code}, just wondering if we could
have condition where the addres comes as localhost or 127.0.0.1
> [YARN-3368] Move new YARN UI configuration to HADOOP_CONF_DIR
> -
>
> Key: YARN-5145
> URL: https://issues.apache.org/jira/browse/YARN-5145
> Project: Hadoop YARN
> Issue Type: Sub-task
>Reporter: Wangda Tan
>Assignee: Sunil G
> Attachments: 0001-YARN-5145-Run-NewUI-WithOldPort-POC.patch,
> YARN-5145-YARN-3368.01.patch, YARN-5145-YARN-3368.02.patch,
> YARN-5145-YARN-3368.03.patch, YARN-5145-YARN-3368.04.patch,
> newUIInOldRMWebServer.png
>
>
> Existing YARN UI configuration is under Hadoop package's directory:
> $HADOOP_PREFIX/share/hadoop/yarn/webapps/, we should move it to
> $HADOOP_CONF_DIR like other configurations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (YARN-5145) [YARN-3368] Move new YARN UI configuration to HADOOP_CONF_DIR
[ https://issues.apache.org/jira/browse/YARN-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15572127#comment-15572127 ] Sunil G edited comment on YARN-5145 at 10/13/16 2:45 PM: - Thanks [~leftnoteasy] for sharing the test results.. I think issue was with CORS from client side. Client also has to query with cors address. I have made necessary changes and tested in 5node cluster where timeline v2 server is running. RM has some config to avoid cors issue, however timeline v2 has cors issue hence we must use corsproxy for timeline v2 for a brief time till timeline supports cors. Hence I have made cors as mandatory in this patch. Pls help to check the same.. cc/[~leftnoteasy] and [~Sreenath] was (Author: sunilg): Thanks [~leftnoteasy] for sharing the test results.. I think there was with CORS from client side. Client also has to query with cors address. I have made necessary changes and tested in 5node cluster where timeline v2 server is running. RM has some config to avoid cors issue, however timeline v2 has cors issue hence we must use corsproxy for timeline v2 for a brief time till timeline supports cors. Hence I have made cors as mandatory in this patch. Pls help to check the same.. cc/[~leftnoteasy] and [~Sreenath] > [YARN-3368] Move new YARN UI configuration to HADOOP_CONF_DIR > - > > Key: YARN-5145 > URL: https://issues.apache.org/jira/browse/YARN-5145 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Wangda Tan >Assignee: Sunil G > Attachments: 0001-YARN-5145-Run-NewUI-WithOldPort-POC.patch, > YARN-5145-YARN-3368.01.patch, YARN-5145-YARN-3368.02.patch, > YARN-5145-YARN-3368.03.patch, newUIInOldRMWebServer.png > > > Existing YARN UI configuration is under Hadoop package's directory: > $HADOOP_PREFIX/share/hadoop/yarn/webapps/, we should move it to > $HADOOP_CONF_DIR like other configurations. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
