hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-6566) Hadoop daemons should not start up if the ownership/permissions on the directories used at runtime are misconfigured
Date Wed, 24 Feb 2010 03:17:32 GMT

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

Arun C Murthy updated HADOOP-6566:
----------------------------------

    Attachment: HADOOP-6566_yhadoop20.patch

Thanks for the review Nicholas, I've incorporated all your comments but for: 

bq. In DiskChecker, how about combining mkdirsWithExistsCheck(..) and checkDir(..) into a
method?

Both methods are used, and hence I've kept them as-is.

bq.     *  You may use FsAction.READ_WRITE, instead of both FsAction.READ and FsAction.WRITE.

I've kept separate checks for better diagnostic errors.

----

I've also changed the implementation of mkdirsWithExistsAndPermissionCheck to use the existing
mkdirsWithExistsCheck(File) since it has very different semantics than java.io.File.mkdirs,
and hence I didn't go about re-inventing it.


> 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.


Mime
View raw message