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

Posted to common-dev@hadoop.apache.org by "Christian Kunz (JIRA)" <ji...@apache.org> on 2007/11/20 04:08:43 UTC

[jira] Commented: (HADOOP-2227) wrong usage of mapred.local.dir.minspacestart

    [ https://issues.apache.org/jira/browse/HADOOP-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543764 ] 

Christian Kunz commented on HADOOP-2227:
----------------------------------------

I have to correct my previous comment, as the map output gets merged into a single file, i.e. free space should not be added up, but when one of the disks has enough space for a task, then TaskTracker.enoughFreeSpace should return true.

> wrong usage of mapred.local.dir.minspacestart 
> ----------------------------------------------
>
>                 Key: HADOOP-2227
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2227
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.15.1
>            Reporter: Christian Kunz
>            Priority: Critical
>
> As I understand it, mapred.local.dir.minspacestart should be used to specify that a map or reduce task requires a minimum disk space to be executed. When several disks are available, and mapred.local.dir lists all of them, then the free space should be added up. But TaskTracker.enoughFreeSpace returns false whenever one of the disks listed in mapred.local.dir has less than the space specified by mapred.local.dir.minspacestart. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.