Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <1924328528.332381268874627477.JavaMail.jira@brutus.apache.org>
Date: Thu, 18 Mar 2010 01:10:27 +0000 (UTC)
From: "Konstantin Boudnik (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-6566) Hadoop daemons should not start up
 if the ownership/permissions on the directories used at runtime are
 misconfigured
In-Reply-To: <1646510502.255391266089668085.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

+1 on the patch. Looks good.

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