[jira] [Assigned] (MAPREDUCE-134) TaskTracker startup fails if any mapred.local.dir entries don't exist

["Ravi Gummadi (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MAPREDUCE-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ravi Gummadi reassigned MAPREDUCE-134:
--------------------------------------

    Assignee: Ravi Gummadi  (was: Owen O'Malley)

> TaskTracker startup fails if any mapred.local.dir entries don't exist
> ---------------------------------------------------------------------
>
>                 Key: MAPREDUCE-134
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-134
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>         Environment: ~30 node cluster, various size/number of disks, CPUs, memory
>            Reporter: Bryan Pendleton
>            Assignee: Ravi Gummadi
>         Attachments: fix-freespace-tasktracker-failure.txt, fix.tasktracker.localdirs.patch.txt
>
>
> This appears to have been introduced with the "check for enough free space" before startup.
> It's debatable how best to fix this bug. I will submit a patch which ignores directories for which the DF utility fails. This is letting me continue operation on my cluster (where the number of drives varies, so there are entries in mapred.local.dir for drives that aren't on all cluster nodes), but a cleaner solution is probably better. I'd lean towards "check for existence", and ignore the dir if it doesn't  - but don't depend on DF to fail, since DF could fail for other reasons without meaning you're out of disk space. I argue that a TaskTracker should start up if *all* directories that *can be written to* in the list have enough space. Otherwise, a failed drive per cluster machine means no work ever gets done.

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