You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2011/01/05 02:34:48 UTC
[jira] Updated: (MAPREDUCE-2234) If Localizer can't create task log
directory, it should fail on the spot
[ https://issues.apache.org/jira/browse/MAPREDUCE-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon updated MAPREDUCE-2234:
-----------------------------------
Attachment: mapreduce-2234.txt
Now with more unit tests, plus some new unit tests for behavior with regard to permissions of mapred.local.dirs during startup.
I'd be interested in people's opinions on something: if some (or all) of the mapred.local.dirs are unwritable when the TT starts up, should it shut itself down?
> If Localizer can't create task log directory, it should fail on the spot
> ------------------------------------------------------------------------
>
> Key: MAPREDUCE-2234
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2234
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: tasktracker
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Attachments: mapreduce-2234.txt, mapreduce-2234.txt
>
>
> Currently, it simply emits a warning. Then, when the taskjvm.sh tries to pipe its output into this directory, it fails with a strange error code like "exit code: 1" which is not intuitive to ops. Instead it should simply throw an exception at initialization time rather than attempting to run the task.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.