[
https://issues.apache.org/jira/browse/TEZ-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15644866#comment-15644866
]
Sreenath Somarajapuram commented on TEZ-3488:
---------------------------------------------
[~jeagles]
bq. The Hadoop cross origin logic Access-Control-Allow-Origin is slightly
different in this case ... Could this be the cause of the issue?
- We have different implementation as the the AM is accessed via RM proxy. And
RM proxy doesn't forward the origin header. In Hadoop logic, the origin is
taken from the requests origin header -
https://github.com/apache/hadoop/blob/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/http/CrossOriginFilter.java#L107
- In a way, we can say that a logic similar to Hadoop code would have prevented
this issue. But that would require RM side changes.
[~gliaw]
bq. What I meant is that if you look at this try catch for setCorsHeaders(),
you can do a check for default ports and strip them:
- That would be good to have.
- But again, is there an use case for adding http://nn1.domain.com:80/tez-ui/
instead of http://nn1.domain.com/tez-ui/ in the configuration?
> 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)
