[ https://issues.apache.org/jira/browse/MAPREDUCE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065485#comment-13065485 ]
Allen Wittenauer commented on MAPREDUCE-2324: --------------------------------------------- > I am more concerned about a sustaining release for the 0.20.20X line If a "real" fix will require a different config param, I'd rather see this bumped to 0.23. This has been a known (and annoying) bug for a long time, but doesn't really require an immediate, sustaining fix if that fix is going to be incomplete and ripped out 6 months later in a newer branch. > 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, 0.20.205.0 > Reporter: Todd Lipcon > Assignee: Robert Joseph Evans > Attachments: MR-2324-security-v1.txt > > > 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