[ https://issues.apache.org/jira/browse/HADOOP-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846596#action_12846596 ]
Konstantin Boudnik commented on HADOOP-6566: -------------------------------------------- Great! Thanks for addressing this. And the last one, I suppose: can these two different patches be joined together to make the scope of modification clearer? > 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-trunk-v4.patch, > hadoop-6566-y20s-d1.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.