hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amareshwari Sri Ramadasu (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2227) wrong usage of mapred.local.dir.minspacestart
Date Wed, 12 Dec 2007 06:36:43 GMT

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

Amareshwari Sri Ramadasu commented on HADOOP-2227:
--------------------------------------------------

In the attached patch,  when one of the disks has enough space for a task, then TaskTracker.enoughFreeSpace
 returns true. The patch also changes localizeJob, localizeTask and localizeCache methods
to use localDirAllocator. 

> 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
>            Assignee: Amareshwari Sri Ramadasu
>            Priority: Critical
>             Fix For: 0.16.0
>
>         Attachments: patch-2227.txt
>
>
> 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.


Mime
View raw message