You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-dev@hadoop.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2011/02/14 19:09:57 UTC

[jira] Created: (MAPREDUCE-2324) Job should fail if a reduce task can't be scheduled anywhere

Job should fail if a reduce task can't be scheduled anywhere
------------------------------------------------------------

                 Key: MAPREDUCE-2324
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2324
             Project: Hadoop Map/Reduce
          Issue Type: Bug
    Affects Versions: 0.20.2
            Reporter: Todd Lipcon


If there's a reduce task that needs more disk space than is available on any mapred.local.dir in the cluster, that task will stay pending forever. For example, we produced this in a QA cluster by accidentally running terasort with one reducer - since no mapred.local.dir had 1T free, the job remained in pending state for several days. The reason for the "stuck" task wasn't clear from a user perspective until we looked at the JT logs.

Probably better to just fail the job if a reduce task goes through all TTs and finds that there isn't enough space.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira