hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil G (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-5698) [YARN-3368] Launch new YARN UI under hadoop web app port
Date Wed, 05 Oct 2016 08:09:20 GMT

     [ https://issues.apache.org/jira/browse/YARN-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sunil G updated YARN-5698:
--------------------------
    Attachment: YARN-5698-YARN-3368.0002.patch


Thanks [~leftnoteasy] for the comments. 

bq.When RM is runs on the local host, we still need to run corsproxy. Do you know what can
we do to fix it?
I have enabled cors-proxy headers in RM as per YARN-4009. With this support, I can launch
and view new YARN web ui w/o corsproxy.

core-site.xml
{noformat}


<property>
  <description>Enable/disable the cross-origin (CORS) filter.</description>
  <name>hadoop.http.cross-origin.enabled</name>
  <value>false</value>
</property>

<property>
  <description>Comma separated list of origins that are allowed for web
    services needing cross-origin (CORS) support. Wildcards (*) and patterns
    allowed</description>
  <name>hadoop.http.cross-origin.allowed-origins</name>
  <value>*</value>
</property>

<property>
  <description>Comma separated list of methods that are allowed for web
    services needing cross-origin (CORS) support.</description>
  <name>hadoop.http.cross-origin.allowed-methods</name>
  <value>GET,POST,HEAD</value>
</property>

<property>
  <description>Comma separated list of headers that are allowed for web
    services needing cross-origin (CORS) support.</description>
  <name>hadoop.http.cross-origin.allowed-headers</name>
  <value>X-Requested-With,Content-Type,Accept,Origin</value>
</property>

<property>
  <description>The number of seconds a pre-flighted request can be cached
    for web services needing cross-origin (CORS) support.</description>
  <name>hadoop.http.cross-origin.max-age</name>
  <value>1800</value>
</property>
{noformat}
yarn-site.xml

{noformat}
<property>
  <description>Flag to enable cross-origin (CORS) support in the RM. This flag
  requires the CORS filter initializer to be added to the filter initializers
  list in core-site.xml.</description>
  <name>yarn.resourcemanager.webapp.cross-origin.enabled</name>
  <value>true</value>
</property>
 <property>
   <description>Flag to enable cross-origin (CORS) support in the NM. This flag
   requires the CORS filter initializer to be added to the filter initializers
   list in core-site.xml.</description>
   <name>yarn.nodemanager.webapp.cross-origin.enabled</name>
   <value>true</value>
 </property>


{noformat}

bq.And if you have some bandwidth, could you test the patch on a distributed environment?
I have tested this in 5-node cluster. Seems fine.


> [YARN-3368] Launch new YARN UI under hadoop web app port
> --------------------------------------------------------
>
>                 Key: YARN-5698
>                 URL: https://issues.apache.org/jira/browse/YARN-5698
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Sunil G
>            Assignee: Sunil G
>         Attachments: YARN-5698-YARN-3368.0001.patch, YARN-5698-YARN-3368.0002.patch
>
>
> As discussed in YARN-5145, it will be better to launch new web ui as a new webapp under
same old port.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message