You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "John Smith (JIRA)" <ji...@apache.org> on 2014/12/10 22:16:15 UTC

[jira] [Assigned] (HADOOP-6590) Add a username check for hadoop sub-commands

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

John Smith reassigned HADOOP-6590:
----------------------------------

    Assignee: John Smith  (was: Allen Wittenauer)

> Add a username check for hadoop sub-commands
> --------------------------------------------
>
>                 Key: HADOOP-6590
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6590
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: scripts
>    Affects Versions: 0.22.0, 3.0.0
>            Reporter: Scott Chen
>            Assignee: John Smith
>            Priority: Minor
>         Attachments: HADOOP-6590-02.patch, HADOOP-6590-03.patch, HADOOP-6590-04.patch, HADOOP-6590-2010-07-12.txt, HADOOP-6590.patch
>
>
> We experienced a case that sometimes we accidentally started HDFS or MAPREDUCE with root user. Then the directory permission will be modified and we have to chown them. It will be nice if there can be a username checking in the hadoop-daemon.sh script so that we always start with the desired username.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)