Can you try whitelisting all the services you have installed in the node? Since this is a Sandbox, ensure all services like Datanode, Namenode etc are whitelisted. ... View more

For Question 2: ensure that you have host names remain the same though the IP's change. Ambari uses Hostnames rather than ip addresses. ... View more

@Kumar Veerappan What are the failure messages? Even if it fails, it's not too difficult to fix it. ... View more

Edit ambari-agent.ini and change alert_grace_period=10 and restart the ambari-agents. This basically increases the grace period for the alerts. This may or may not work. But give it a try. ... View more

Ok, this could be accessed only by customers who have purchased support license. Which version of Ambari are yo uusing? ... View more

@Muthukumar S Please refer to KB Article 000004014 and increase the grace times. ... View more

@Jagdish Saripella Do you have AMS up and running? Do the operations go faster if you stop AMS service? ... View more

@revan wabale Also verify and ensure that hadoop.proxyuser.hive.users/group are set to * in hdfs-configs [core-site]. ... View more

@Gaurav Gupta Create your own Repo of plain hadoop and provide those repo link as repositories in Ambari. ... View more

@Muthukumar S How did you change hadoop.tmp.dir? ... View more

@revan wabale I was going through HDFS ACL Use Cases. It does look like most of the use cases can be achieved using Ranger. I'm not sure about the Sticky bit + ACL scenario though. Is there a particular use case you are looking at? ... View more

@mrizvi It just takes time for Ambari to show the correct status. This should go good in the next release of Zeppelin. ... View more

@Srikaran Jangidi Try restarting the agent in the node and also try to re-install the clients in this node. ... View more

@sharath chandra parashara Please review the Namenode log files to see if the checkpoint has been successful. ... View more

@Srikaran Jangidi At this moment, 'embedded'/'distributed' decides only about where the AMS collected data is stored. Distributed only means the data collected by AMS is stored in HDFS and nothing else. It uses only the local resource except for HDFS. In embedded mode, the AMS data is stored in a physical file in the location defined in /etc/ams-hbase/conf/hbase-site.xml and resides local to the node where the collector is running. Currently, there is only one Region Server in the Standalone Hbase used by AMS. Slowly AMS has started using cluster resources - for example, in the recent releases, the Cluster zookeeper could be used. At some point, we might have multiple region servers spread across the nodes in cluster as well. ... View more

@Muthukumar S / @Rahul Pathak Shouldn't the parameter be - mapreduce.cluster.temp.dir Please review descriptions for mapred-default.xml. By default it goes to ${hadoop.tmp.dir}/mapred/temp. I'm hoping setting this should help. Also it would be useful to find the parameter for and change hadoop.tmp.dir ... View more

@Vinod Nerella It looks like the Zeppelin is already installed. I hope you have followed the steps to add Zeppelin stack to Ambari as described in the link above. Do a yum list installed and check if zeppelin is already installed - if, so try removing the same using rpm -ev zeppelin and then try to install. Thanks & Rgds Venkat ... View more

@Aman Mundra Please try restarting the Namenode and datanodes and then try to start the services. ... View more

@Shiva Moorthy Could you please try restarting the metadata database [postgres?] and ambari-server? ... View more

@Shihab Do you have Tez jobs running in the setup for adhoc queries? Are the queues configured as documented here: Using Tez with Hive Especially, the following: <property> <name>hive.server2.tez.default.queues</name> <value>default</value> </property> <property> <name>hive.server2.tez.sessions.per.default.queue</name> <value>1</value> </property> If there are going to simultaneous connections, more queues need to be defined and each queue should have 2-5 sessions. ... View more