hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Yang (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7893) Sort out tarball conf directories
Date Thu, 08 Dec 2011 05:15:40 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-7893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13164999#comment-13164999

Eric Yang commented on HADOOP-7893:

There should be only one template copy which has been utilized by hadoop-setup-conf.sh to
jump start new comer to configure hadoop clusters.


It seems there are certain artifacts left over from project refactoring.  Some clean up would
be nice.
> Sort out tarball conf directories
> ---------------------------------
>                 Key: HADOOP-7893
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7893
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.23.0
>            Reporter: Eli Collins
> The conf directory situation in the tarball (generated by mvn pacakge -Dtar) is a mess.
The top-level conf directory just contains mr2 conf, there are two other incomplete conf dirs:
> {noformat}
> hadoop-0.24.0-SNAPSHOT $ ls conf/
> slaves  yarn-env.sh  yarn-site.xml
> hadoop-0.24.0-SNAPSHOT $ find . -name conf
> ./conf
> ./share/hadoop/hdfs/templates/conf
> ./share/hadoop/common/templates/conf
> {noformat}
> yet there are 4 hdfs-site.xml files:
> {noformat}
> hadoop-0.24.0-SNAPSHOT $ find . -name hdfs-site.xml
> ./etc/hadoop/hdfs-site.xml
> ./share/hadoop/hdfs/templates/conf/hdfs-site.xml
> ./share/hadoop/hdfs/templates/hdfs-site.xml
> ./share/hadoop/common/templates/conf/hdfs-site.xml
> {noformat}
> And it looks like ./share/hadoop/common/templates/conf contains the old MR1 style conf
(eg mapred-site.xml).
> We should generate a tarball with a single conf directory that just has common, hdfs
and mr2 confs.

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


View raw message