ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-13693) Ambari Blueprint sets inconsistent Yarn RM values
Date Tue, 03 Nov 2015 22:40:27 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-13693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14988321#comment-14988321
] 

Hudson commented on AMBARI-13693:
---------------------------------

FAILURE: Integrated in Ambari-branch-2.1 #792 (See [https://builds.apache.org/job/Ambari-branch-2.1/792/])
AMBARI-13693. Ambari Blueprint sets inconsistent Yarn RM values (DIPAYAN (sgunturi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=80d36ec7c0f2ccf51a2f62253bfb60b9234ba1ce])
* contrib/views/utils/src/test/java/org/apache/ambari/view/utils/ambari/ServicesTest.java
* contrib/views/utils/src/main/java/org/apache/ambari/view/utils/ambari/Services.java


> Ambari Blueprint sets inconsistent Yarn RM values
> -------------------------------------------------
>
>                 Key: AMBARI-13693
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13693
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-views
>    Affects Versions: 2.1.2
>            Reporter: DIPAYAN BHOWMICK
>            Assignee: DIPAYAN BHOWMICK
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-13693_branch-2.1.patch
>
>
> Steps to reproduce; 
> 1. Deploy with blueprint with RM HA enabled
> 2. Blueprint doesnot set "yarn.resourcemanager.webapp.address.rm1" and "yarn.resourcemanager.webapp.address.rm2"
properties to yarn-site.xml
> 3. Select TEZ view
> {code} 
> 20 Oct 2015 15:24:52,247 WARN [qtp-client-30] ServletHandler:563 - /api/v1/views/TEZ/versions/0.7.0.2.3.2.0-378/instances/TEZ_CLUSTER_INSTANCE/resources/status

> java.lang.NullPointerException 
> at org.apache.ambari.view.utils.ambari.Services.getRMHAUrls(Services.java:124) 
> at org.apache.ambari.view.utils.ambari.Services.getRMUrlFromClusterConfig(Services.java:94)

> at org.apache.ambari.view.utils.ambari.Services.getRMUrl(Services.java:74) 
> at org.apache.ambari.view.tez.ViewControllerImpl.getViewStatus(ViewControllerImpl.java:60)

> at org.apache.ambari.view.tez.rest.ViewStatusResource.getViewStatus(ViewStatusResource.java:44)

> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

> at java.lang.reflect.Method.invoke(Method.java:483) 
> at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)

> at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
> {code}
> Expectation is that "${yarn.resourcemanager.hostname.rm1/rm2}:DEFAULT_RM_WEBAPP_PORT"
will be used instead to fetch the Active RM Url



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message