[
https://issues.apache.org/jira/browse/BIGTOP-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Shaposhnik updated BIGTOP-316:
------------------------------------
Attachment: BIGTOP-316.patch2.txt
Bruno, thanks a million for a very nice and helpful feedback. I've attached a
patch that now builds on RPM and takes care of some of your concerns (home for
daemons and %preun).
To answer your other questions:
1. Where does ${bin_wrapper/hadoop/yarn} come from?
That's just a hack to have hadoop launcher script include yarn. Ugly, but
it'll go away as much as the rest of HADOOP-7939 related things. I suggest we
just keep it for now.
2. Any reason to set hadoop.tmp.dir to /var/lib/hdfs/cache/${user.name}
instead of /var/lib/hdfs/cache/${user.name}/tmp
The hadoop.tmp.dir is not really a tmp dir, but more of a prefix for other
things that Hadoop constructs on the fly if they are not setup explicitly.
Thanks,
Roman.
> 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, BIGTOP-316.patch2.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
