Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 21 Mar 2016 17:15:25 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12950787.1458119127000.6696.1458580525844@Atlassian.JIRA>
In-Reply-To: <JIRA.12950787.1458119127000@Atlassian.JIRA>
References: <JIRA.12950787.1458119127000@Atlassian.JIRA>
 <JIRA.12950787.1458119127015@arcas>
Subject: [jira] [Commented] (AMBARI-15438) Capacity Scheduler view is not
 working when using custom configuration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/AMBARI-15438?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D15=
204653#comment-15204653 ]=20

Hudson commented on AMBARI-15438:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #4522 (See [https://builds.apach=
e.org/job/Ambari-trunk-Commit/4522/])
AMBARI-15438. Capacity Scheduler view is not working when using custom (dip=
ayan.bhowmick: [http://git-wip-us.apache.org/repos/asf?p=3Dambari.git&a=3Dc=
ommit&h=3De80464cd0917f4b9afa7946e03593746c64bb2b2])
* contrib/views/utils/src/main/java/org/apache/ambari/view/utils/ambari/Rem=
oteCluster.java


> Capacity Scheduler view is not working when using custom configuration
> ----------------------------------------------------------------------
>
>                 Key: AMBARI-15438
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15438
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-views
>    Affects Versions: 2.2.1
>            Reporter: Gaurav Nagar
>            Assignee: Gaurav Nagar
>             Fix For: 2.2.2
>
>         Attachments: AMBARI-15438_branch-2.2.patch
>
>
> Capacity scheduler not working when using remote cluster.
> It fails to get ranger-yarn-plugin configuration when ranger service is n=
ot installed.
> http://c6408.ambari.apache.org:8080/api/v1/views/CAPACITY-SCHEDULER/versi=
ons/1.0.0/instances/AUTO_CS_INSTANCE/resources/scheduler/configuration/getC=
onfig?siteName=3Dranger-yarn-plugin-properties&configName=3Dranger-yarn-plu=
gin-enabled
> {code:java}
> {"trace":"java.lang.NullPointerException\n\tat org.apache.ambari.view.uti=
ls.ambari.RemoteCluster.getConfigurationValue(RemoteCluster.java:80)\n\tat =
org.apache.ambari.view.capacityscheduler.ConfigurationService.getConfigurat=
ionValue(ConfigurationService.java:494)\n\tat sun.reflect.NativeMethodAcces=
sorImpl.invoke0(Native Method)\n\tat sun.reflect.NativeMethodAccessorImpl.i=
nvoke(NativeMethodAccessorImpl.java:62)\n\tat sun.reflect.DelegatingMethodA=
ccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat java.lang.re=
flect.Method.invoke(Method.java:497)\n\tat com.sun.jersey.spi.container.Jav=
aMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat com.=
sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatch=
Provider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvide=
r.java:205)\n\tat com.sun.jersey.server.impl.model.method.dispatch.Resource=
JavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat c=
om.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.ja=
va:302)\n\tat com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept=
(RightHandPathRule.java:147)\n\tat=20
> {code}


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