HDP-2.3.4.7-4 Ambari Version 2.2.1.1 All services are up and running except for History server. Could not find any related errors in namenode or data node logs. Following is the error reported by Ambari. File "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py", line 191, in run_command raise Fail(err_msg) resource_management.core.exceptions.Fail: Execution of 'curl -sS -L -w '%{http_code}' -X PUT -T /usr/hdp/2.3.4.7-4/hadoop/mapreduce.tar.gz 'http://standbynamenode.sample.com:50070/webhdfs/v1/hdp/apps/2.3.4.7-4/mapreduce/mapreduce.tar.gz?op=CREATE&user.name=hdfs&overwrite=True&permission=444'' returned status_code=403. { "RemoteException": { "exception": "ConnectException", "javaClassName": "java.net.ConnectException", "message": "Call From datanode.sample.com/10.250.98.101 to localhost:8020 failed on connection exception: java.net.ConnectException: Connection refused; For more details see: http://wiki.apache.org/hadoop/ConnectionRefused" } } Status code: 403 indicates that the request is correct, but not probably authroized? Any pointers will be helpful. Thanks, ... View more

Wanted to set up HA (active name node and standby name node)cluster. We did not want to have a secondary name node to be present. Just two name nodes and one of them will be active and the other as standby. Used the Ambari blueprint exactly as outlined in the link: https://cwiki.apache.org/confluence/display/AMBARI/Blueprint+Support+for+HA+Clusters Getting an error: {\n "status" : 400,\n "message" : "Cluster Topology validation failed. Invalid service component count: [SECONDARY_NAMENODE(actual=0, required=1)]. To disable topology validation and create the blueprint, add the following to the end of the url: \'?validate_topology=false\'"\n} Tried to disable topology validation with validate_topology=false, Blueprint registered but while creating cluster creation failed with the error given below java.util.concurrent.ExecutionException: java.lang.Exception: java.lang.IllegalArgumentException: Unable to update configuration property 'dfs.namenode.https-address' with topology information. Component 'NAMENODE' is mapped to an invalid number of hosts '2'. Any pointers to sort this out will be very helpful. Thanks, Mohan ... View more