https://community.cloudera.com/t5/Archives-of-Support-Questions/Datanode-failure/m-p/98640#M12026 <P>Under what circumstances we could notice map-reduce job getting failed/terminated when one of datanode goes down ?</P> Fri, 11 Dec 2015 05:36:00 GMT ahshanmd 2015-12-11T05:36:00Z https://community.cloudera.com/t5/Archives-of-Support-Questions/Datanode-failure/m-p/98640#M12026 <P>Under what circumstances we could notice map-reduce job getting failed/terminated when one of datanode goes down ?</P> Fri, 11 Dec 2015 05:36:00 GMT https://community.cloudera.com/t5/Archives-of-Support-Questions/Datanode-failure/m-p/98640#M12026 ahshanmd 2015-12-11T05:36:00Z https://community.cloudera.com/t5/Archives-of-Support-Questions/Datanode-failure/m-p/98641#M12027 <P>MapReduce job would not fail on a typical HDP cluster unless there is only one Datanode+Node Manager in the cluster. MapReduce tasks would fail on the datanode if datanode goes down but the same failed tasks on failed node (Datanode+NM) would be allocated on other datanodes where other replica of Data is present and MR job would continue.</P> Fri, 11 Dec 2015 06:03:29 GMT https://community.cloudera.com/t5/Archives-of-Support-Questions/Datanode-failure/m-p/98641#M12027 pardeep_kumar 2015-12-11T06:03:29Z https://community.cloudera.com/t5/Archives-of-Support-Questions/Datanode-failure/m-p/98642#M12028 <P>Golden rule for MRv2 an Hadoop cluster should always be an odd number of data nodes 3,5,7,9 etc because of the distributed workload architecture any failed job is automatically restarted on the surviving data nodes. remember to configure the mapred.sites.xml parameter mapreduce.jobtracker.restart.recover parameter to TRUE and dont forget to set the number of tries in the mapreduce.map.maxattempts parameter in the mapred-default.xml</P> Fri, 11 Dec 2015 06:20:46 GMT https://community.cloudera.com/t5/Archives-of-Support-Questions/Datanode-failure/m-p/98642#M12028 Shelton 2015-12-11T06:20:46Z