hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7518) Unable to start HDFS cluster on trunk (after the common mavenisation)
Date Fri, 05 Aug 2011 17:43:27 GMT

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

Alejandro Abdelnur commented on HADOOP-7518:


Current times are not several minutes, actually it is faster than 20secs for a prebuild run:

* Building the tar from clean (mvn clean package -DskipTests -Ptar) takes 30secs
* Building the tar from a pre-built (mvn package -DskipTests -Ptar) takes 17secs

Still, I've opened HADOOP-7497 a couple of days ago to make things faster as per your suggestion.

> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message