hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MAPREDUCE-4555) make user's mapred .staging area permissions configurable
Date Wed, 03 Oct 2012 05:10:11 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-4555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alejandro Abdelnur resolved MAPREDUCE-4555.
-------------------------------------------

    Resolution: Not A Problem

These restrictions are by design.
                
> make user's mapred .staging area permissions configurable
> ---------------------------------------------------------
>
>                 Key: MAPREDUCE-4555
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4555
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: client, job submission
>    Affects Versions: 1.0.3
>            Reporter: Alexander Alten-Lorenz
>
> The directories are created in JobTracker and LocalRunner, but they are currently forced
to be 0700. There is even a segment of the source code that will check the permissions are
0700, and if not it will change the permissions to match 0700. For monitoring purposes the
permissions should be configurable.
> Please note:
> 1. We can make the hard-coded 700 configurable at clients (its the client who creates
it) but there's two issues here: 
> 1.1. It violates security principals (as its client sided and overridable) 
> 1.2. It can't be consistent, since some user may ignore configs provided to them and
create it with 0700.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message