[ http://issues.apache.org/jira/browse/HADOOP-578?page=comments#action_12444875 ] Sanjay Dahiya commented on HADOOP-578: --------------------------------------
ok, i'll make it start searching at index 0. The only issue i see with that is if speculative instances are configured to start, and conditions satisfy for speculative execution when tasks start failing then it may be a better idea to run failed tasks first and then speculative tasks on available cluster resources. > Failed tasks should not be put at the end of the job tracker's queue > -------------------------------------------------------------------- > > Key: HADOOP-578 > URL: http://issues.apache.org/jira/browse/HADOOP-578 > Project: Hadoop > Issue Type: Improvement > Components: mapred > Affects Versions: 0.6.2 > Reporter: Owen O'Malley > Assigned To: Sanjay Dahiya > > This functionality was basically a workaround for other problems, which have > been fixed. The impact of putting them at the end of the work queue is that > if you have 100,000 maps, and the Mapper fails deterministically, you'll run > 300,000+ attempts before your job is killed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
