[
https://issues.apache.org/jira/browse/HADOOP-5850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712691#action_12712691
]
Vinod K V commented on HADOOP-5850:
-----------------------------------
This situation occurs if scheduler is invoked and it calls
job.obtainNewMapTask() while the job-clean-up task of this job is still
running. Discussed with this Devaraj who concurs that
obtainNewMapTask()/obtainNewReduceTask() should return immediately, doing
nothing, when job-cleanup is running. Will address this in a new JIRA.
> map/reduce doesn't run jobs with 0 maps
> ---------------------------------------
>
> Key: HADOOP-5850
> URL: https://issues.apache.org/jira/browse/HADOOP-5850
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.20.0
> Reporter: Owen O'Malley
> Assignee: Vinod K V
> Priority: Critical
> Fix For: 0.20.1
>
> Attachments: HADOOP-5850-20090519.1.txt, HADOOP-5850-20090519.txt,
> HADOOP-5850-20090520-svn-branch-20.v2.txt, HADOOP-5850-20090520-svn.1.txt,
> HADOOP-5850-20090522-branch-20-final.txt, HADOOP-5850-20090522.txt,
> screenshot-1.jpg
>
>
> Currently, the framework ignores jobs that have 0 maps. This is incorrect.
> Many pipelines need the job to run (if nothing else, to create the output
> directory!) so that subsequent jobs don't fail. Effectively, there will be no
> map tasks and the reduce tasks should immediately set up the Reducer and
> RecordWriter and then call close on both since there are no inputs to the
> reduce. I believe it should just work if we remove the check...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
