incubator-bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruno Mahé (Commented) (JIRA) <j...@apache.org>
Subject [jira] [Commented] (BIGTOP-478) perhaps we should go back to mapred as a user name for mapreduce daemons in Hadoop 0.23
Date Thu, 22 Mar 2012 00:15:26 GMT

    [ https://issues.apache.org/jira/browse/BIGTOP-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13235242#comment-13235242
] 

Bruno Mahé commented on BIGTOP-478:
-----------------------------------

+1
                
> perhaps we should go back to mapred as a user name for mapreduce daemons in Hadoop 0.23
> ---------------------------------------------------------------------------------------
>
>                 Key: BIGTOP-478
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-478
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.4.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.4.0
>
>         Attachments: BIGTOP-478.patch.txt
>
>
> In the early days of Hadoop 0.23 the thinking went that might be better off having a
"mapreduce" user id for the hadoop mapreduce daemons. Since then folks have been complaining
that:
>   # mapreduce doesn't get displayed by ps (it is too long)
>   # it is different from Hadoop 1.0 daemons packaging
>   # in a kerberized deployment it is confusing to have 2 types of principals
> Personally, I'm fully convinced now that going back to 'mapred' as a user name is reasonable.
The patch is also pretty trivial. I'll attach it and you guys can let me know if there's a
reason we shouldn't apply it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message