ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-15438) Capacity Scheduler view is not working when using custom configuration
Date Mon, 21 Mar 2016 17:12:25 GMT

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

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

FAILURE: Integrated in Ambari-branch-2.2 #537 (See [https://builds.apache.org/job/Ambari-branch-2.2/537/])
AMBARI-15438. Capacity Scheduler view is not working when using custom (dipayan.bhowmick:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=953150fea90810712443d4a187d80486613bf33c])
* contrib/views/utils/src/main/java/org/apache/ambari/view/utils/ambari/RemoteCluster.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 not installed.
> http://c6408.ambari.apache.org:8080/api/v1/views/CAPACITY-SCHEDULER/versions/1.0.0/instances/AUTO_CS_INSTANCE/resources/scheduler/configuration/getConfig?siteName=ranger-yarn-plugin-properties&configName=ranger-yarn-plugin-enabled
> {code:java}
> {"trace":"java.lang.NullPointerException\n\tat org.apache.ambari.view.utils.ambari.RemoteCluster.getConfigurationValue(RemoteCluster.java:80)\n\tat
org.apache.ambari.view.capacityscheduler.ConfigurationService.getConfigurationValue(ConfigurationService.java:494)\n\tat
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)\n\tat
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
java.lang.reflect.Method.invoke(Method.java:497)\n\tat com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat

> {code}



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

Mime
View raw message