@Shihab What is the engine used? If you do the following does it work: hive -hiveconf hive.execution.engine=mr Please invoke hive as follows and see where it is failing: hive -hiveconf hive.root.logger=DEBUG,console any errors would be thrown in the console, read through the same to identify the root cause. Thanks & Rgds Venkat ... View more

@Eric Periard Please use this article and see if the previous upgrade went good using, Using Ambari to check when upgrade / downgrade seem to be stuck If everything looks good for the hosts / versions [ie there shouldn't be any in INSTALL_FAILED state], then the finalization could help - else those need to be fixed first. ... View more

@Aman Mundra Try to restart NN services using Ambari post installation. If it fails to come up, review the namenode log file to find what the issue is. ... View more

You could install a Standalone Ambari server for the purpose of Ambari View. Please check Standalone Ambari Views server in the Same. There aren't any other solution from HDP which would support your requirement. ... View more

@Kaliyug Antagonist Setup a Local Repository in this scenario. Refer to Ambari Install guide for the same. ... View more

@Facundo Bianco Is it a fresh installation of the cluster? It's strange that in a fresh cluster installation, there are entries in alert_notice table. What is observed when you do a select * from alert_notice ? how many rows are returned? Please backup the database using mysql dump and then try to remove a row from this table to check the privileges [without committing] ... View more

@charan tej You have to setup Ambari-Views to achieve this. Please review Ambari Views guide for the same. ... View more

@Robert Mroczkowski the only change management which is available is config change management as pointed out by @Sri Bandaru A limited change management with respect to services / components can be achieved by manually backing up Ambari db before doing any changes, ... View more

@suresh krish Is this a test system? Are the values for the following modified from default dfs.namenode.checkpoint.period, set to 1 hour by default, specifies the maximum delay between two consecutive checkpoints dfs.namenode.checkpoint.txns, set to 1 million by default, defines the number of uncheckpointed transactions on the NameNode which will force an urgent checkpoint, even if the checkpoint period has not been reached. You could go to the Namenode current folder and check when was the last fsimage created. Was the cluster down for long? You may want to review the above two parameters and check the timestamps in the current folder and find why automatic checkpointing is not happening. You could use the steps provided by @Sri Bandaru to do a checkpoint manually if you could get downtime. ... View more

Are you connected to the hbase master system as listed by Ambari? If so, hbase isn't correctly installed for some reason. Is this a test cluster? If so please remove HBase using API and add it back using Ambari add service. You could refer Cwik pages for the same. ... View more