[
https://issues.apache.org/jira/browse/MAPREDUCE-6494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated MAPREDUCE-6494:
-------------------------------------
Attachment: MAPREDUCE-6494.003.patch
We actually found one last permissions issue. If using the
DefaultContainerExecutor, the shells are run as the Yarn user who won't have
permission to operate on the temp dir when it's permissions are using 700. The
003 patch changes it to use 770 permissions to fix this.
> Permission issue when running archive-logs tool as different users
> ------------------------------------------------------------------
>
> Key: MAPREDUCE-6494
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6494
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 2.8.0
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Attachments: MAPREDUCE-6494.001.patch, MAPREDUCE-6494.002.patch,
> MAPREDUCE-6494.003.patch
>
>
> If the tool is run as user A, it creates {{/tmp/logs/archive-logs-work}} for
> temp work, but doesn't delete it. When it's run again as user B, you can run
> into permissions problems on {{/tmp/logs/archive-logs-work}} because user B
> doesn't have permission to do anything to that dir (it's 700). We should
> have the tool delete {{/tmp/logs/archive-logs-work}} when exiting.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
