hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-2219) JT should not try to remove mapred.system.dir during startup
Date Wed, 05 Jan 2011 22:16:47 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978002#action_12978002
] 

Tom White commented on MAPREDUCE-2219:
--------------------------------------

This looks like a good change. A couple of comments:

* Can you use FileUtil#fullyDeleteContents() rather than writing a new one?
* The comment in the test for 755 perms should say "rwxr-xr-x" not "rwx-rx-rx".

> 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.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.


Mime
View raw message