Workaround could only is replicated to 0 nodes, instead of 1

Solution could only is replicated to 0 nodes, instead of 1 blog categories: Small record ~ Beware ~ hadoopreplicated to 0 nodes&http://www.aliyun.com/ Zixun/aggregation/37954.html ">nbsp; After you open the start-all.sh script for Hadoop, perform an example that shows properties could only being replicated to 0 nodes, instead of 1, and the solution is:
1. Stop Hadoop script: bin/stop-all.sh
(Note data backup before 2, 3 steps)
2. Delete the master node and the temporary folder from the HADOOP root directory on the node, such as $hadoop_home/hadooptmp
3. Format Namenode:hadoop Namenode-format
4, re-open Hadoop start-all.sh script: bin/start-all.sh
5, see if the Datanode from the node is up, no words repeat 2, 3
6, execute the desired jar package
Normal Appearance:
INFO input. Fileinputformat:total input paths to Process:2
INFO util.820.html ">nativecodeloader:loaded the Native-hadoop Library
INFO mapred. Jobclient:running job:job_201303111150_0001
INFO mapred. Jobclient:map vs Reduce 0%
INFO mapred. Jobclient:map 100% Reduce 0%
INFO mapred. Jobclient:map 100% Reduce 100%
INFO mapred. Jobclient:job complete:job_201303111150_0001