[
https://issues.apache.org/jira/browse/HADOOP-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846548#action_12846548
]
Konstantin Boudnik commented on HADOOP-6566:
--------------------------------------------
Patch seems to be good and the little Mockito extension is neat. Although, it
adds up a different way of wotking with mocks, which might be confusing
somewhat.
However, I still can see failing test if a user umask settings are different
from expected. I again suggest to make changes in MiniDFSCluster to make sure
that it creates service directories with correct permissions. Otherwise, this
is the change which introduce an implicit environment assumption i.e. bad idea!
> 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
> Affects Versions: 0.22.0
> Reporter: Devaraj Das
> Assignee: Arun C Murthy
> Fix For: 0.22.0
>
> Attachments: hadoop-6566-trunk-v1.patch, hadoop-6566-trunk-v2.patch,
> hadoop-6566-trunk-v3.patch, 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.
