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

Jerry Chen commented on HADOOP-9260:
------------------------------------

I tried to find the problem that why this random phenomenon happens even at the 
runtime.

The problem lies on the class path using to load the 
common-version-info.properties. I checked that the 
common-version-info.properties file in the hadoop-common-3.0.0-SNAPSHOT.jar has 
the right information. But it loaded from another 
common-version-info.properties file which is in the 
hadoop-common-3.0.0-SNAPSHOT-sources.jar( when sources was packaged). While the 
values of common-version-info.properties file in the 
hadoop-common-3.0.0-SNAPSHOT-sources.jar are uninitialized and thus shows 
values such as ${pom.version}.

In some environments, the hadoop-common-3.0.0-SNAPSHOT-sources.jar may appear 
after hadoop-common-3.0.0-SNAPSHOT.jar in the class path. But in some others, 
it map appear before and cause problems.

I checked that in trunk version without this problem, the 
common-version-info.properties doesn't exists in 
hadoop-common-3.0.0-SNAPSHOT-sources.jar. So it has no problem.
                
> Hadoop version commands show incorrect information on trunk
> -----------------------------------------------------------
>
>                 Key: HADOOP-9260
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9260
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: trunk-win
>            Reporter: Jerry Chen
>            Priority: Critical
>
> 1. Check out the trunk from 
> http://svn.apache.org/repos/asf/hadoop/common/trunk/ 
> 2. Compile package
>    m2 package -Pdist -Psrc -Pnative -Dtar -DskipTests
> 3. Hadoop version of compiled dist shows the following:
> Hadoop ${pom.version}
> Subversion ${version-info.scm.uri} -r ${version-info.scm.commit}
> Compiled by ${user.name} on ${version-info.build.time}
> From source with checksum ${version-info.source.md5}
> And in a real cluster, the log in name node shows:
> 2013-01-29 15:23:42,738 INFO org.apache.hadoop.hdfs.server.namenode.NameNode: 
> STARTUP_MSG: 
> /************************************************************
> STARTUP_MSG: Starting NameNode
> STARTUP_MSG:   host = bdpe01.sh.intel.com/10.239.47.101
> STARTUP_MSG:   args = []
> STARTUP_MSG:   version = ${pom.version}
> STARTUP_MSG:   classpath = ...
> STARTUP_MSG:   build = ${version-info.scm.uri} -r ${version-info.scm.commit}; 
> compiled by '${user.name}' on ${version-info.build.time}
> STARTUP_MSG:   java = 1.6.0_33
> While some data nodes with the same binary shows the correct version 
> information.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to