[
https://issues.apache.org/jira/browse/HADOOP-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587096#action_12587096
]
Amareshwari Sriramadasu commented on HADOOP-3182:
-------------------------------------------------
job-output-dir, job-history-dir and job-temp-dir can have the permissions as
644.
bq. Are profile.getJobFile()).getParent() and new Path(conf.getSystemDir(),
jobId) supposed to be different?
Yes. It looks like they are the same directories. One of the deletes can be
removed.
To be specific, fs.delete(new Path(profile.getJobFile()).getParent(),
true); can be removed.
bq. What is the usage of FileUtil.fullyDelete? Is it the same as
FileSystem.delete(path, recursive=true)?
Yes they are the same.
bq. job-dir/job.xml (aka jobconf, create-setPerm by JobClient; Should it be
visible in JobTracker webpage??? It is visible now.)
Yes. It should be visible :)
> JobClient creates submitJobDir with SYSTEM_DIR_PERMISSION ( rwx-wx-wx)
> ----------------------------------------------------------------------
>
> Key: HADOOP-3182
> URL: https://issues.apache.org/jira/browse/HADOOP-3182
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.16.2
> Reporter: lohit vijayarenu
> Assignee: Tsz Wo (Nicholas), SZE
> Priority: Blocker
> Fix For: 0.16.3, 0.17.0
>
> Attachments: 3182_20080408.patch, 3182_20080408_0.16.patch
>
>
> JobClient creates submitJobDir with SYSTEM_DIR_PERMISSION ( rwx-wx-wx ) which
> causes problem while sharing a cluster.
> Consider the case where userA starts jobtracker/tasktrackers and userB
> submits a job to this cluster. When userB creates submitJobDir it is created
> with rwx-wx-wx which cannot be read by tasktracker started by userA
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
