[
https://issues.apache.org/jira/browse/HADOOP-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833599#action_12833599
]
Steve Loughran commented on HADOOP-6566:
----------------------------------------
options
# make any check downgradable to a message logged at warning/info/debug
# just do a check that you can read/write content in the dir
# Make it an option to drop any dir that isn't considered secure, but only fail
if the number of directories for each role falls below a specified number.
Not being able to read/write files, bad news. Having the clock in that dir
significantly off from your time, potentially trouble, though on network
mounted filesystems not always a complete surprise.
> 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
> Fix For: 0.22.0
>
>
> 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.
