[BIGTOP-1174] missing dependency setting on init-hdfs.sh in puppet recipes

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.7.0
• Fix Version/s: 0.8.0
• Component/s: deployment
• Assignee: Sean Mackrory
• Reporter: Evans Ye
• Created: 06/Jan/14 17:09
• Updated: 12/May/14 18:15
• Resolved: 22/Jan/14 02:07

Description

There's no dependency setting to explicitly define init-hdfs.sh to be executed after hdfs get ready, so when running the puppet recipes to deploy a hadoop environment, the init-hdfs.sh script failed to setup folders and permissions on hdfs since it will be executed before namenode and datanode has been started.

Sample output:

notice: /Stage[main]/Hadoop_worker_node/Hadoop::Datanode[datanode]/File[/data/1/hdfs]/mode: mode changed '0700' to '0755'
notice: /Stage[main]/Hadoop_head_node/Exec[init hdfs]/returns: executed successfully
notice: /Stage[main]/Hadoop_worker_node/Hadoop::Datanode[datanode]/File[/data/2/hdfs]/mode: mode changed '0700' to '0755'
notice: /Stage[main]/Hadoop_worker_node/Hadoop::Datanode[datanode]/Service[hadoop-hdfs-datanode]/ensure: ensure changed 'stopped' to 'running'
notice: /Stage[main]/Hadoop_head_node/Hadoop::Namenode[namenode]/Service[hadoop-hdfs-namenode]/ensure: ensure changed 'stopped' to 'running'
notice: /Stage[main]/Hadoop_head_node/Hadoop-hbase::Master[hbase master]/Service[hbase-master]/ensure: ensure changed 'stopped' to 'running'
notice: Finished catalog run in 135.44 seconds

Issue Links

• is duplicated by: BIGTOP-922 Existing Puppet recipes are failing to initialize HDFS dictories on the first run