@Jay SenSharma @Geoffrey Shelton Okot Thank you. I have been able to change the affected tables to InnoDB with the ALTER statement. However, on restarting ambari-server, there was another error related to the atlas configs in the clusterconfigmapping table; 2017-06-02 13:31:11,549 WARN - You have config(s): [atlas-solrconfig, atlas-logsearch-conf, atlas-env, atlas-log4j, ranger-atlas-security, ranger-atlas-policymgr-ssl, application-properties, ranger-atlas-plugin-properties] that is(are) not mapped (in clusterconfigmapping table) to any cluster! 2017-06-02 13:31:11,560 ERROR - Required config(s): atlas-solrconfig,atlas-logsearch-conf,atlas-env,atlas-log4j,application-properties is(are) not available for service ATLAS with service config version 2 in cluster XXXX ... View more

@Scott Aslan I don't see any javascript errors in the dev tools console of Chrome/Firefox. ... View more

@Matt Clarke Yes, i am able to add a new controller but not edit it. ... View more

@Sebastian Carroll I have checked in Chrome and Firefox. It's the same issue. ... View more

Yes, the datanodes crashed @Arpit Agarwal. hdfs dfsadmin -report command is more accurate in reporting the datanode failure. ... View more

Hello @Arpit Agarwal, the errors are quite frequent and I just restarted 2 data nodes now. Infact, 4 out of 8 data nodes have been restarted in the last 6 hours. ... View more

@zkfs Failed datanode is still listed in Ambari UI but there is a connection failed alert and running the hdfs dfsadmin -report command shows the dead datanodes. ... View more

@Namit Maheshwari Please find attached the log. ... View more