[jira] [Created] (AMBARI-13693) Ambari Blueprint sets inconsistent Yarn RM values

["DIPAYAN BHOWMICK (JIRA)" <ji...@apache.org>]

DIPAYAN BHOWMICK created AMBARI-13693:
-----------------------------------------

             Summary: 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
             Fix For: 2.1.3


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)