You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Madhuvanthi Radhakrishnan (JIRA)" <ji...@apache.org> on 2017/09/11 17:52:00 UTC
[jira] [Assigned] (AMBARI-21865) NullPointerException during
blueprint generation
[ https://issues.apache.org/jira/browse/AMBARI-21865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Madhuvanthi Radhakrishnan reassigned AMBARI-21865:
--------------------------------------------------
Assignee: Madhuvanthi Radhakrishnan
> NullPointerException during blueprint generation
> ------------------------------------------------
>
> Key: AMBARI-21865
> URL: https://issues.apache.org/jira/browse/AMBARI-21865
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.3
> Reporter: amarnath reddy pappu
> Assignee: Madhuvanthi Radhakrishnan
> Fix For: 2.6.0
>
>
> PROBLEM:
> When customer tries to access Ambari Blueprint:
> http://Ambarihost:8080/api/v1/clusters/TEST?format=blueprint
> They see below error message web UI:
> { "status": 500, "message": "Server Error" }
> 7 Aug 2017 22:14:06,516 ERROR ambari-client-thread-214895 ContainerResponse:419 - The RuntimeException could not be mapped to a response, re-throwing to the HTTP container
> java.lang.NullPointerException
> at org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.splitAndTrimStrings(BlueprintConfigurationProcessor.java:1176)
> at org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.parseNameNodes(BlueprintConfigurationProcessor.java:930)
> Customer has setup a configuration for remote servers which are HA in their configs.
> They started seeing this after making those changes.
> dfs.namenode.http-address.nonha=<local-cluster-NN-IP>:50070
> dfs.nameservices.internal=nonha
> dfs.nameservices=nonha,hacluster
> dfs.namenode.rpc-address.nonha=<local-cluster-NN-IP>:8020
> dfs.namenode.rpc-address.hacluster.nn2=<remote-cluster-NN1-IP>:8020
> dfs.namenode.rpc-address.hacluster.nn1=<remote-cluster-NN2-IP>:8020
> dfs.ha.namenodes.hacluster=nn1,nn2
> dfs.client.failover.proxy.provider.hacluster=org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider
> Basically dfs.ha.namenodes.NNSERVICE value is not defined and it errors out.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)