[ 
https://issues.apache.org/jira/browse/HADOOP-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842003#action_12842003
 ] 

Konstantin Boudnik commented on HADOOP-6566:
--------------------------------------------

A nasty side effect of this modification is that now a user's environment 
settings affect the result of test test. Which clearly shouldn't happen. I.e. I 
have umask=002 and all of sadden my test runs start to fail because 
dfs.data.dir has incorrect permissions.

Ideally, test environment should guarantee that environment is properly set 
before making any assumptions or assertions.

> Hadoop daemons should not start up if the ownership/permissions on the 
> directories used at runtime are misconfigured
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-6566
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6566
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: security
>            Reporter: Devaraj Das
>            Assignee: Arun C Murthy
>             Fix For: 0.22.0
>
>         Attachments: HADOOP-6566_yhadoop20.patch, 
> HADOOP-6566_yhadoop20.patch, HADOOP-6566_yhadoop20.patch, 
> HADOOP-6566_yhadoop20.patch
>
>
> The Hadoop daemons (like datanode, namenode) should refuse to start up if the 
> ownership/permissions on directories they use at runtime are misconfigured or 
> they are not as expected. For example, the local directory where the 
> filesystem image is stored should be owned by the user running the namenode 
> process and should be only readable by that user. We can provide this feature 
> in common and HDFS and MapReduce can use the same.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to