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

Harsh J commented on HADOOP-8055:
---------------------------------

Mahadev,

>From hadoop-assemblies' {{assemblies/hadoop-dist.xml}} all the target does is 
>take each project's src/main/conf and place it inside etc/conf. This change is 
>inline with empty configs inside other projects (hdfs, httpfs for example) and 
>these reflect inside the tar already. Unsure how yarn gets them in, however, 
>cause they do not carry such a dir in any of their projects. Perhaps that's 
>why they don't appear under etc/hadoop?

Is the template sourcing is only done for packages, and not the tar assembly?

In any case, we'd have to pick one method up and use it for all projects. 
Please do reopen this issue if this current way of injecting core-site.xml is 
incorrect!
                
> Distribution tar.gz does not contain etc/hadoop/core-site.xml
> -------------------------------------------------------------
>
>                 Key: HADOOP-8055
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8055
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.24.0
>            Reporter: Eric Charles
>            Assignee: Harsh J
>             Fix For: 0.24.0, 0.23.2
>
>         Attachments: HADOOP-8055.patch, HADOOP-8055.patch
>
>
> A dist built from trunk (0.24.0-SNAPSHOT) does not contain a core-site.xml in 
> $HADOOP_HOME/etc/hadoop/ folder.
> $HADOOP_HOME/sbin/start-dfs.sh without that folder gives an exception
> Exception in thread "main" java.lang.IllegalArgumentException: URI has an 
> authority component
>  at java.io.File.<init>(File.java:368)
>  at 
> org.apache.hadoop.hdfs.server.namenode.NNStorage.getStorageDirectory(NNStorage.java:310)
>  at org.apache.hadoop.hdfs.server.namenode.FSEditLog.init(FSEditLog.java:178)
> ...
> Manually creating $HADOOP_HOME/etc/hadoop/core-site.xml solves this problem 
> and hadoop starts fine.

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

        

Reply via email to