[jira] [Comment Edited] (TEZ-3488) Tez UI Vertex 404
[
https://issues.apache.org/jira/browse/TEZ-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15629594#comment-15629594
]
George Liaw edited comment on TEZ-3488 at 11/2/16 4:59 PM:
---
[~Sreenath] [~jeagles]
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:
https://github.com/apache/tez/blob/master/tez-dag/src/main/java/org/apache/tez/dag/app/web/AMWebController.java#L127
Could be rewritten as:
{code:java}
try {
URL url = new URL(historyUrlBase);
if (url.getPort() == 80 || url.getPort() == 443) {
origin = url.getProtocol() + "://" + url.getHost();
} else {
origin = url.getProtocol() + "://" + url.getHost() + ":" +
url.getPort();
}
} catch (MalformedURLException e) {
if (LOG.isDebugEnabled()) {
LOG.debug("Invalid url set for tez history url base: " +
historyUrlBase, e);
}
}
{code}
was (Author: gliaw):
[~Sreenath] [~jeagles]
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:
https://github.com/apache/tez/blob/master/tez-dag/src/main/java/org/apache/tez/dag/app/web/AMWebController.java#L127
{code:java}
try {
URL url = new URL(historyUrlBase);
if (url.getPort() == 80 || url.getPort() == 443) {
origin = url.getProtocol() + "://" + url.getHost();
} else {
origin = url.getProtocol() + "://" + url.getHost() + ":" +
url.getPort();
}
} catch (MalformedURLException e) {
if (LOG.isDebugEnabled()) {
LOG.debug("Invalid url set for tez history url base: " +
historyUrlBase, e);
}
}
{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 @ "
> 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)
[jira] [Comment Edited] (TEZ-3488) Tez UI Vertex 404
[
https://issues.apache.org/jira/browse/TEZ-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15623543#comment-15623543
]
George Liaw edited comment on TEZ-3488 at 11/1/16 12:06 AM:
[~jeagles] The corresponding settings found at the /conf url are below. Looks
like hadoop.http.cross-origin.enabled was set programatically.
{code:xml}
hadoop.http.cross-origin.enabled
true
programatically
yarn.resourcemanager.webapp.cross-origin.enabled
true
java.io.BufferedInputStream@41fbdac4
hadoop.http.filter.initializers
org.apache.hadoop.http.lib.StaticUserWebFilter,org.apache.hadoop.security.HttpCrossOriginFilterInitializer
core-site.xml
{code}
was (Author: gliaw):
[~jeagles] The corresponding settings found at the /conf url are below. Looks
like hadoop.http.cross-origin.enabled was set programatically.
{code:xml}
hadoop.http.cross-origin.enabled
true
programatically
yarn.resourcemanager.webapp.cross-origin.enabled
true
java.io.BufferedInputStream@41fbdac4
hadoop.http.filter.initializers
org.apache.hadoop.http.lib.StaticUserWebFilter,org.apache.hadoop.security.HttpCrossOriginFilterInitializer
core-site.xml
{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 @ "
> 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)
[jira] [Comment Edited] (TEZ-3488) Tez UI Vertex 404
[
https://issues.apache.org/jira/browse/TEZ-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15623318#comment-15623318
]
George Liaw edited comment on TEZ-3488 at 10/31/16 8:36 PM:
[~jeagles] [~Sreenath]
Our hadoop is version 2.7.2 so the multiple initializers should be good on that
point.
Current error message:
{code}
Error code: Unknown, message: Failed to fetch dagProgress. Application Master
(AM) is out of reach. Either it's down, or CORS is not enabled for YARN
ResourceManager.
Could not retrieve expected data from Resource Manager @
http://rm1.domain.com:8088/proxy/application_1477918050351_0710/ws/v1/tez/dagProgress?dagID=2
{code}
Listed url returns:
{code}
{
"dagProgress": {
"id": "dag_1477918050351_0710_2",
"progress": 1
}
}
{code}
was (Author: gliaw):
[~jeagles] [~Sreenath]
Our hadoop is version 2.7.2 so the multiple initializers should be good on that
point.
Current error message:
{code}
Error code: Unknown, message: Failed to fetch dagProgress. Application Master
(AM) is out of reach. Either it's down, or CORS is not enabled for YARN
ResourceManager.
Could not retrieve expected data from Resource Manager @
http://rm1.domain.com:8088/proxy/application_1477918050351_0710/ws/v1/tez/dagProgress?dagID=2
{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 @ "
> 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)
[jira] [Comment Edited] (TEZ-3488) Tez UI Vertex 404
[
https://issues.apache.org/jira/browse/TEZ-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15623318#comment-15623318
]
George Liaw edited comment on TEZ-3488 at 10/31/16 8:34 PM:
[~jeagles] [~Sreenath]
Our hadoop is version 2.7.2 so the multiple initializers should be good on that
point.
Current error message:
{code}
Error code: Unknown, message: Failed to fetch dagProgress. Application Master
(AM) is out of reach. Either it's down, or CORS is not enabled for YARN
ResourceManager.
Could not retrieve expected data from Resource Manager @
http://rm1.domain.com:8088/proxy/application_1477918050351_0710/ws/v1/tez/dagProgress?dagID=2
{code}
was (Author: gliaw):
[~jeagles] [~Sreenath]
Our hadoop is version 2.7.2 so the multiple initializers should be good on that
point.
> 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 @ "
> 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)
[jira] [Comment Edited] (TEZ-3488) Tez UI Vertex 404
[ https://issues.apache.org/jira/browse/TEZ-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15622451#comment-15622451 ] Jonathan Eagles edited comment on TEZ-3488 at 10/31/16 3:22 PM: Support for cross origin filters in the resource manager proxy service was added as part of YARN-4009 was first released as part of Hadoop 2.7.2. This does support multiple initializers but should only need to be turned on at the RM. [~gliaw], can you confirm what version of hadoop and if that version of hadoop has cross origin support in the RM. was (Author: jeagles): Support for cross origin filters in the resource manager proxy service was added as part of https://issues.apache.org/jira/browse/YARN-4009 was first released as part of Hadoop 2.7.2. This does support multiple initializers but should only need to be turned on at the RM. [~gliaw], can you confirm what version of hadoop and if that version of hadoop has cross origin support in the RM. > 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 @ " > 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)
[jira] [Comment Edited] (TEZ-3488) Tez UI Vertex 404
[
https://issues.apache.org/jira/browse/TEZ-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15616697#comment-15616697
]
George Liaw edited comment on TEZ-3488 at 10/28/16 9:50 PM:
[~Sreenath] [~hitesh]
Thanks for the advice. I've tried pushing out these configs, but still getting
this error:
{code}
Could not retrieve expected data from Resource Manager @
http://rm1.domain.com:8088/proxy/application_1477690015764_0001/ws/v2/tez/verticesInfo?dagID=1==
{code}
If I go to that url, I get json for the vertices.
CORS-related configs used:
core-site:
{code:xml}
hadoop.http.filter.initializers
org.apache.hadoop.http.lib.StaticUserWebFilter,org.apache.hadoop.security.HttpCrossOriginFilterInitializer
hadoop.http.cross-origin.enabled
true
{code}
yarn-site:
{code:xml}
Enables cross-origin support (CORS) for web services where
cross-origin web response headers are needed. For example, javascript
making
a web services request to the timeline server.
yarn.timeline-service.http-cross-origin.enabled
true
yarn.resourcemanager.webapp.cross-origin.enabled
true
yarn.nodemanager.webapp.cross-origin.enabled
true
{code}
Tried looking up "yarn.webservices.http-cross-origin.enabled" and I don't see
it as an available config?
was (Author: gliaw):
[~Sreenath] [~hitesh]
Thanks for the advice. I've tried pushing out these configs, but still getting
this error:
{code}
Could not retrieve expected data from Resource Manager @
http://rm1.domain.com:8088/proxy/application_1477690015764_0001/ws/v2/tez/verticesInfo?dagID=1==
{code}
CORS-related configs used:
core-site:
{code:xml}
hadoop.http.filter.initializers
org.apache.hadoop.http.lib.StaticUserWebFilter,org.apache.hadoop.security.HttpCrossOriginFilterInitializer
hadoop.http.cross-origin.enabled
true
{code}
yarn-site:
{code:xml}
Enables cross-origin support (CORS) for web services where
cross-origin web response headers are needed. For example, javascript
making
a web services request to the timeline server.
yarn.timeline-service.http-cross-origin.enabled
true
yarn.resourcemanager.webapp.cross-origin.enabled
true
yarn.nodemanager.webapp.cross-origin.enabled
true
{code}
Tried looking up "yarn.webservices.http-cross-origin.enabled" and I don't see
it as an available config?
> 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 @ "
> 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)
