bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruno Mahé (Issue Comment Edited) (JIRA) <j...@apache.org>
Subject [jira] [Issue Comment Edited] (BIGTOP-316) split up hadoop packages into common, hdfs, mapreduce (and yarn)
Date Wed, 11 Jan 2012 03:23:41 GMT

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

Bruno Mahé edited comment on BIGTOP-316 at 1/11/12 3:23 AM:
------------------------------------------------------------

Overall, it looks great! 
Some notes:
* Any reason to set hadoop.tmp.dir to /var/lib/hdfs/cache/${user.name} instead of /var/lib/hdfs/cache/${user.name}/tmp
? 
* I don't really like moving /usr/libexec to /usr/lib/hadoop/libexec. But if it makes it work,
I don't really have choice.
* Where does ${bin_wrapper/hadoop/yarn} come from?
* I would set hdfs user's homedir to /var/lib/hdfs. Same for other users (I know it's not
new)
* the %preun in hdfs, yarn and mapreduce in the spec file won't work. the %service_macro will
take care of the services. So please delete these %preun sections

                
      was (Author: bmahe):
    Overall, it looks great! 
Some notes:
* Any reason to set hadoop.tmp.dir to /var/lib/hdfs/cache/${user.name} instead of /var/lib/hdfs/cache/${user.name}/tmp
? 
* I don't really like moving /usr/libexec to /usr/lib/hadoop/libexec. But if it makes it work,
I don't really have choice.
* Where does ${bin_wrapper/hadoop/yarn} come from?
* I would set hdfs user's homedir to /var/lib/hdfs. Same for other users (I know it's not
new)
* the %preun in hdfs, yarn and mapreduce in the spec file won't work. the %service_macro will
take care of that. So please delete these sections.

                  
> split up hadoop packages into common, hdfs, mapreduce (and yarn)
> ----------------------------------------------------------------
>
>                 Key: BIGTOP-316
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-316
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.3.0
>
>         Attachments: BIGTOP-316.patch.txt
>
>
> Here are the new names I would like to propose in hadoop-0.23 branch:
>  * hadoop (for hadoop-common, but since it won't be limited to just the hadoop-common
project it is hadoop)
>  * hadoop-hdfs
>  * hadoop-yarn
>  * hadoop-mapreduce
>  * hadoop-hdfs-namenode
>  * hadoop-hdfs-secondarynamenode
>  * hadoop-hdfs-datanode
>  * hadoop-yarn-resourcemanager
>  * hadoop-yarn-nodemanager
>  * hadoop-mapreduce-historyserver
>  * hadoop-libhdfs
>  * hadoop-conf-pseudo
>  * hadoop-docs
> given that they look a tad too long, an alternative would be to drop hadoop- prefix and
go with
> the shorter versions (even though technically all these projects are *sub* projects of
Hadoop):
>  * hadoop
>  * hadoop-conf-pseudo
>  * hadoop-docs
>  * hdfs
>  * yarn
>  * mapreduce
>  * hdfs-namenode
>  * hdfs-secondarynamenode
>  * hdfs-datanode
>  * yarn-resourcemanager
>  * yarn-nodemanager
>  * mapreduce-historyserver
>  * libhdfs
>  * hadoop-conf-pseudo
>  * hadoop-docs
> Please leave your opinion on which one is better in the comments section.
> P.S. Quick search over at http://pkgs.org revealed no name clashes for both
> long and short versions.

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