Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

namenode search needs logic to find itself on first-boot #2

Open
clifferson opened this issue Mar 22, 2012 · 0 comments
Open

namenode search needs logic to find itself on first-boot #2

clifferson opened this issue Mar 22, 2012 · 0 comments

Comments

@clifferson
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant