Ambari is not able to start the Namenode

I have a workaround to make it work under ambari environment:

• In the ambari node modify:

  • /usr/lib/ambari-server/web/javascripts/app.js
  • /usr/lib/ambari-server/web/javascripts/app.js.map

changing from:

{"name": "dfs.namenode.secondary.http-address","templateName": ["snamenode_host"],"foreignKey": null,"value": "<templateName[0]>:50090","filename": "hdfs-site.xml"},

to the specific value for your secondary namenode and not the template one:

{"name": "dfs.namenode.secondary.http-address","templateName": ["snamenode_host"],"foreignKey": null,"value": "my.secondary.namenode.domain:50090","filename": "hdfs-site.xml"},

• rename /usr/lib/ambari-server/web/javascripts/app.js.gz to /usr/lib/ambari-server/web/javascripts/app.js.gz.old

• gzip the app.js so a new app.js.gz is generated in the same directory

• Refresh your ambari web and force an HDFS restart, this will regenerate the appropiate /etc/hadoop/conf/hdfs-site.xml, if it does not, you coud add in the ambari web a new property and then delete it in order to force the changes when you press the save button.

Hope this helps.

--mLG

Partially fixed: it is necessary to stop all the HDFS services (Journal Node, Namenodes and Datanodes) before editing the hdfs-site.xml file. Then, of course, Ambari "start button" cannot be used because the configuration would be smashed... thus it is necessary to re-start all the services manually. This is not the definitive solution since it is desirable this changes of configuration could be done from Ambari UI...