You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/08/08 23:53:12 UTC
[jira] [Resolved] (HADOOP-7518) Unable to start HDFS cluster on
trunk (after the common mavenisation)
[ https://issues.apache.org/jira/browse/HADOOP-7518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer resolved HADOOP-7518.
--------------------------------------
Resolution: Won't Fix
I'm going to close this as won't fix. it's pretty much impossible to fix this post-mavenization without at least setting where HADOOP_LIBEXEC_DIR lives.
> Unable to start HDFS cluster on trunk (after the common mavenisation)
> ---------------------------------------------------------------------
>
> Key: HADOOP-7518
> URL: https://issues.apache.org/jira/browse/HADOOP-7518
> Project: Hadoop Common
> Issue Type: Bug
> Components: scripts
> Reporter: Vinod Kumar Vavilapalli
> Attachments: Patch
>
>
> This is what I do:
> In common directory:
> mvn package -Pbintar -Dmaven.test.skip.exec=true
> cp target/hadoop-common-0.23.0-SNAPSHOT-bin.tar.gz ~/tmp/common/
> In hdfs directory:
> ant veryclean binary -Dresolvers=internal
> cp build/hadoop-hdfs-0.23.0-SNAPSHOT-bin.tar.gz ~/tmp/hdfs/
> Untar the tarballs, and start namenode as follows:
> {quote}
> export HADOOP_COMMON_HOME=~vinodkv/tmp/common/hadoop-common-0.23.0-SNAPSHOT-bin;
> export HADOOP_CONF_DIR=~vinodkv/tmp/conf;
> export HADOOP_HDFS_HOME=~vinodkv/tmp/hdfs/hadoop-hdfs-0.23.0-SNAPSHOT;
> $HADOOP_COMMON_HOME/sbin/hadoop-daemon.sh start namenode
> {quote}
> The last one simply says "Hadoop common not found." and exits.
--
This message was sent by Atlassian JIRA
(v6.2#6252)