[
https://issues.apache.org/jira/browse/HADOOP-3835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617757#action_12617757
]
Steve Loughran commented on HADOOP-3835:
----------------------------------------
Thinking about this a bit more, a big choice point is does the hadoop-site.xml
file get distributed as an RPM, or is managed in other ways? If it is also
pushed out by RPM, then it should be a separate RPM that Apache don't
distributed themselves, but let people push out. It should also be stored in
the filesystem layout such that people who use the RPM are happy. This is
somewhat controversial.
1. the Filesystem Hierarchy Standard [
http://www.pathname.com/fhs/pub/fhs-2.3.html ] says conf files should go into
/var/opt/, so there should be a directory /var/opt/hadoop containing hadoop
configuration files, which can be customised on a per-machine basis.
2. If you are managing a datacentre, you dont want things customised on a
per-machine basis, as that creates problems. You want a single configuration
for the entire cluster. And you dont want to mount /var/opt/hadoop using NFS,
as that just creates a SPOF in the cluster.
Which argues for putting the configuration files into /opt/hadoop along with
everything else, and somehow pushing that configuration out.
It is a lot easier to do #1; letting people downstream do their own RPMs is
powerful, but complicated.
see also:
http://smartfrog.svn.sourceforge.net/viewvc/smartfrog/trunk/core/release/doc/creating_and_editing_rpms.pdf
> Develop scripts to create rpm package to facilitate deployment of hadoop on
> Linux machines
> ------------------------------------------------------------------------------------------
>
> Key: HADOOP-3835
> URL: https://issues.apache.org/jira/browse/HADOOP-3835
> Project: Hadoop Core
> Issue Type: Improvement
> Components: build
> Reporter: dhruba borthakur
> Priority: Minor
>
> A rpm-like packing scheme to package and then install hadoop binaries is very
> helpful, especially when the number of machines in the cluster is huge.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
