[
https://issues.apache.org/jira/browse/TEZ-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15623528#comment-15623528
]
Jonathan Eagles commented on TEZ-3488:
--------------------------------------
[~gliaw], can you check some RM settings for me to verify settings are correct.
http://rm1.domain.com:8088/conf
Specifically check, the value
{code:xml}
<property>
<name>hadoop.http.cross-origin.enabled</name>
<value>true</value>
<source>programatically</source>
</property>
{code}
{code:xml}
<property>
<name>yarn.resourcemanager.webapp.cross-origin.enabled</name>
<value>true</value>
<source>yarn-site.xml</source>
</property>
{code}
{code:xml}
<property>
<name>hadoop.http.filter.initializers</name>
<value>customfilter1,customfilter2,org.apache.hadoop.security.HttpCrossOriginFilterInitializer</value>
<source>core-site.xml</source>
</property>
{code}
Obviously the customfilter1 and customfilter2 are my edited versions, but it
shows that a comma separated list does work. Note the origin of the
configurations. The programmatic setting means the RM read the
yarn.resourcemanager.webapp.cross-origin.enabled setting and programmatically
set the hadoop.http.cross-origin.enabled for that service. Please tell me if
that setting was set programmatically.
> Tez UI Vertex 404
> -----------------
>
> Key: TEZ-3488
> URL: https://issues.apache.org/jira/browse/TEZ-3488
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.8.4
> Reporter: George Liaw
>
> When we're trying to view vertices for a running job, the Vertex page will
> show a 404 error saying:
> "Could not retrieve expected data from @ <url>"
> And the Vertex Counter page will show:
> "Counters unavailable"
> and
> "Error code: Unknown, message: Resource Manager (RM) out of reach. Either
> it's down or CORS is not enabled"
> The RMs are up and CORS is enabled. If we go to the displayed url, we get the
> expected XML with the application info. When the DAG finishes running, those
> errors go away and the pages display fine. Any idea what's going on here?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
