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/06 03:13:47 UTC
[jira] Updated: (MAPREDUCE-2219) JT should not try to remove
mapred.system.dir during startup
[ https://issues.apache.org/jira/browse/MAPREDUCE-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon updated MAPREDUCE-2219:
-----------------------------------
Attachment: mapreduce-2219.2.txt
This patch fixes the permissions string in the comment, nice catch.
Unfortunately I couldn't use FileUtil.fullyDeleteContents because that method takes File and not Path/FileSystem. Rather than filing a second JIRA to add that method to common, I just implemented it inline since it's pretty straightforward.
> JT should not try to remove mapred.system.dir during startup
> ------------------------------------------------------------
>
> Key: MAPREDUCE-2219
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2219
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobtracker
> Affects Versions: 0.22.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Attachments: mapreduce-2219.2.txt, mapreduce-2219.txt
>
>
> During startup, the JT tries to clean up mapred.system.dir by recursively removing it and then recreating it. This requires that mapred.system.dir is inside a directory owned by the mapred user. For example, if set to /system/mapred then /system must be owned by the mapred account. This isn't documented properly and also seems unnecessary. Instead we can remove the *contents* of mapred.system.dir instead of the directory itself.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.