[
https://issues.apache.org/jira/browse/TEZ-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15615579#comment-15615579
]
Sreenath Somarajapuram commented on TEZ-3488:
---------------------------------------------
[~premal] & [~gliaw]
bq. If we go to the displayed url, we get the expected XML with the application
info.
That statement makes it look more like a RM CORS issue.
bq. When the DAG finishes running, those errors go away and the pages display
fine. Any idea what's going on here?
We use RM only for realtime data. For finished DAGs pages display fine, as RM
APIs are not used.
Please help me with these questions also:
- Are you running the UI via Ambari or in stand alone mode?
- What all configurations have been set to enable RM CORS?
> 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)
