You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first time you boot strap a name node it searches for it self for fs.default.name to build a config file. If it dosent find it self (it wont because its not saved on the chef server yet) the config file is built missing the value and namenode service wont start.
"search" should check node.run_list.includes?("recipe[cloudera::hadoop_namenode") if search is empty
The text was updated successfully, but these errors were encountered:
The first time you boot strap a name node it searches for it self for fs.default.name to build a config file. If it dosent find it self (it wont because its not saved on the chef server yet) the config file is built missing the value and namenode service wont start.
"search" should check node.run_list.includes?("recipe[cloudera::hadoop_namenode") if search is empty
The text was updated successfully, but these errors were encountered: