[
https://issues.apache.org/jira/browse/TEZ-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15627736#comment-15627736
]
George Liaw commented on TEZ-3488:
----------------------------------
[~Sreenath] [~jeagles]
Okay, figured out the issue. The tez.tez-ui.history-url.base in tez-site.xml
had listed port 80, so the allowed origin header was explicitly looking for
port 80 in the origin, which the browser does not send.
I don't know if anyone would like change Tez to strip ports 80 and 443 from the
config setting before using the url in the allowed origin header, but otherwise
people will just have to be aware that this is a special case to look at if the
error shown says Application Master out of reach.
Example of problematic config in tez-site.xml:
{code:xml}
<property>
<description>URL for where the Tez UI is hosted</description>
<name>tez.tez-ui.history-url.base</name>
<value>http://nn1.domain.com:80/tez-ui/</value>
</property>
{code}
> 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)
