[jira] [Commented] (HADOOP-9260) Hadoop version may be not correct when starting name node or data node

2013-02-06 Thread Hudson (JIRA)

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

Hudson commented on HADOOP-9260:


Integrated in Hadoop-Mapreduce-trunk #1336 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1336/])
HADOOP-9260. Hadoop version may be not correct when starting name node or 
data node. Contributed by Chris Nauroth (Revision 1442639)

 Result = SUCCESS
jlowe : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1442639
Files : 
* 
/hadoop/common/trunk/hadoop-assemblies/src/main/resources/assemblies/hadoop-dist.xml
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt


> Hadoop version may be not correct when starting name node or data node
> --
>
> 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
>Assignee: Chris Nauroth
>Priority: Critical
> Fix For: 2.0.3-alpha
>
> Attachments: HADOOP-9260.1.patch
>
>
> 1. Check out the trunk from 
> http://svn.apache.org/repos/asf/hadoop/common/trunk/ -r 1439752
> 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


[jira] [Commented] (HADOOP-9260) Hadoop version may be not correct when starting name node or data node

2013-02-06 Thread Hudson (JIRA)

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

Hudson commented on HADOOP-9260:


Integrated in Hadoop-Hdfs-trunk #1308 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1308/])
HADOOP-9260. Hadoop version may be not correct when starting name node or 
data node. Contributed by Chris Nauroth (Revision 1442639)

 Result = SUCCESS
jlowe : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1442639
Files : 
* 
/hadoop/common/trunk/hadoop-assemblies/src/main/resources/assemblies/hadoop-dist.xml
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt


> Hadoop version may be not correct when starting name node or data node
> --
>
> 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
>Assignee: Chris Nauroth
>Priority: Critical
> Fix For: 2.0.3-alpha
>
> Attachments: HADOOP-9260.1.patch
>
>
> 1. Check out the trunk from 
> http://svn.apache.org/repos/asf/hadoop/common/trunk/ -r 1439752
> 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


[jira] [Commented] (HADOOP-9260) Hadoop version may be not correct when starting name node or data node

2013-02-06 Thread Hudson (JIRA)

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

Hudson commented on HADOOP-9260:


Integrated in Hadoop-Yarn-trunk #119 (See 
[https://builds.apache.org/job/Hadoop-Yarn-trunk/119/])
HADOOP-9260. Hadoop version may be not correct when starting name node or 
data node. Contributed by Chris Nauroth (Revision 1442639)

 Result = FAILURE
jlowe : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1442639
Files : 
* 
/hadoop/common/trunk/hadoop-assemblies/src/main/resources/assemblies/hadoop-dist.xml
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt


> Hadoop version may be not correct when starting name node or data node
> --
>
> 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
>Assignee: Chris Nauroth
>Priority: Critical
> Fix For: 2.0.3-alpha
>
> Attachments: HADOOP-9260.1.patch
>
>
> 1. Check out the trunk from 
> http://svn.apache.org/repos/asf/hadoop/common/trunk/ -r 1439752
> 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


[jira] [Commented] (HADOOP-9260) Hadoop version may be not correct when starting name node or data node

2013-02-05 Thread Hudson (JIRA)

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

Hudson commented on HADOOP-9260:


Integrated in Hadoop-trunk-Commit #3324 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/3324/])
HADOOP-9260. Hadoop version may be not correct when starting name node or 
data node. Contributed by Chris Nauroth (Revision 1442639)

 Result = SUCCESS
jlowe : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1442639
Files : 
* 
/hadoop/common/trunk/hadoop-assemblies/src/main/resources/assemblies/hadoop-dist.xml
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt


> Hadoop version may be not correct when starting name node or data node
> --
>
> 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
>Assignee: Chris Nauroth
>Priority: Critical
> Fix For: 2.0.3-alpha
>
> Attachments: HADOOP-9260.1.patch
>
>
> 1. Check out the trunk from 
> http://svn.apache.org/repos/asf/hadoop/common/trunk/ -r 1439752
> 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


[jira] [Commented] (HADOOP-9260) Hadoop version may be not correct when starting name node or data node

2013-02-04 Thread Jerry Chen (JIRA)

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

Jerry Chen commented on HADOOP-9260:


+1 By applying the patch, the sources jar are put to separate sources folder 
and the problem is resolved.
Thanks,
Jerry

> Hadoop version may be not correct when starting name node or data node
> --
>
> 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
>Assignee: Chris Nauroth
>Priority: Critical
> Attachments: HADOOP-9260.1.patch
>
>
> 1. Check out the trunk from 
> http://svn.apache.org/repos/asf/hadoop/common/trunk/ -r 1439752
> 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


[jira] [Commented] (HADOOP-9260) Hadoop version may be not correct when starting name node or data node

2013-02-04 Thread Jason Lowe (JIRA)

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

Jason Lowe commented on HADOOP-9260:


+1, changes look good to me and is aligned with HADOOP-9116 wrt. source jar 
placement.  Giving Jerry some time to kick the tires on the patch before 
committing.

> Hadoop version may be not correct when starting name node or data node
> --
>
> 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
>Assignee: Chris Nauroth
>Priority: Critical
> Attachments: HADOOP-9260.1.patch
>
>
> 1. Check out the trunk from 
> http://svn.apache.org/repos/asf/hadoop/common/trunk/ -r 1439752
> 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


[jira] [Commented] (HADOOP-9260) Hadoop version may be not correct when starting name node or data node

2013-02-04 Thread Chris Nauroth (JIRA)

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

Chris Nauroth commented on HADOOP-9260:
---

No tests, because it's a change in the build only.

> Hadoop version may be not correct when starting name node or data node
> --
>
> 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
>Assignee: Chris Nauroth
>Priority: Critical
> Attachments: HADOOP-9260.1.patch
>
>
> 1. Check out the trunk from 
> http://svn.apache.org/repos/asf/hadoop/common/trunk/ -r 1439752
> 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


[jira] [Commented] (HADOOP-9260) Hadoop version may be not correct when starting name node or data node

2013-02-04 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on HADOOP-9260:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12567884/HADOOP-9260.1.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  The javadoc tool did not generate any 
warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 1.3.9) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-assemblies.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/2143//testReport/
Console output: 
https://builds.apache.org/job/PreCommit-HADOOP-Build/2143//console

This message is automatically generated.

> Hadoop version may be not correct when starting name node or data node
> --
>
> 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
>Assignee: Chris Nauroth
>Priority: Critical
> Attachments: HADOOP-9260.1.patch
>
>
> 1. Check out the trunk from 
> http://svn.apache.org/repos/asf/hadoop/common/trunk/ -r 1439752
> 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


[jira] [Commented] (HADOOP-9260) Hadoop version may be not correct when starting name node or data node

2013-01-30 Thread Jason Lowe (JIRA)

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

Jason Lowe commented on HADOOP-9260:


Agree that we should move the source jars off the classpath.  +1 for taking 
just the source jars portion of HADOOP-9116 in the short term to fix this 
issue, then HADOOP-9116 can complete the move of test jars off the classpath 
when we decide how to resolve the running of tests issue.


> Hadoop version may be not correct when starting name node or data node
> --
>
> 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/ -r 1439752
> 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


[jira] [Commented] (HADOOP-9260) Hadoop version may be not correct when starting name node or data node

2013-01-30 Thread Chris Nauroth (JIRA)

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

Chris Nauroth commented on HADOOP-9260:
---

Jerry, thank you for the details.  That helps clarify the problem.  I would not 
expect the HADOOP-9246 patch to fix the problem that you're seeing.

I think we need to revisit HADOOP-8723 (patch from [~jlowe]) or HADOOP-9116 
(patch from [~tucu00]).  The goal of both of these issues is to remove the test 
and source jars from the runtime classpath, because they can cause odd problems 
like this.  There was some question about those patches potentially making it 
more awkward to run tests, so they haven't been committed yet.  If we need a 
compromise, then maybe we could just move the source jar out of the way for now 
and revisit moving the test jar off of the classpath later.  We only need to 
move the source jar out of the way to resolve HADOOP-9260, and it's definitely 
not correct to have the source jar on the classpath.


> Hadoop version may be not correct when starting name node or data node
> --
>
> 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/ -r 1439752
> 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


[jira] [Commented] (HADOOP-9260) Hadoop version may be not correct when starting name node or data node

2013-01-30 Thread Jerry Chen (JIRA)

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

Jerry Chen commented on HADOOP-9260:


The incorrect version would cause more problems when running MapReduce jobs 
even if the cluster seems to start as normal. For example, when running Hive 
queries, the query failed at random and the log shows:

2013-01-30 15:45:37,080 WARN [main] org.apache.hadoop.mapred.YarnChild: 
Exception running child : java.lang.RuntimeException: 
java.lang.reflect.InvocationTargetException
at 
org.apache.hadoop.util.ReflectionUtils.newInstance(ReflectionUtils.java:128)
at 
org.apache.hadoop.io.serializer.WritableSerialization$WritableDeserializer.deserialize(WritableSerialization.java:66)
at 
org.apache.hadoop.io.serializer.WritableSerialization$WritableDeserializer.deserialize(WritableSerialization.java:42)
at org.apache.hadoop.mapred.MapTask.getSplitDetails(MapTask.java:370)
at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:402)
at org.apache.hadoop.mapred.MapTask.run(MapTask.java:341)
at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:158)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at 
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1452)
at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:153)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at 
org.apache.hadoop.util.ReflectionUtils.newInstance(ReflectionUtils.java:126)
... 10 more
Caused by: java.lang.NumberFormatException: For input string: "${pom"
at 
java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:449)
at java.lang.Integer.parseInt(Integer.java:499)
at 
org.apache.hadoop.hive.shims.ShimLoader.getMajorVersion(ShimLoader.java:125)
at org.apache.hadoop.hive.shims.ShimLoader.loadShims(ShimLoader.java:92)
at 
org.apache.hadoop.hive.shims.ShimLoader.getHadoopShims(ShimLoader.java:66)
at 
org.apache.hadoop.hive.ql.io.CombineHiveInputFormat$CombineHiveInputSplit.(CombineHiveInputFormat.java:85)
... 15 more


> Hadoop version may be not correct when starting name node or data node
> --
>
> 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/ -r 1439752
> 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


[jira] [Commented] (HADOOP-9260) Hadoop version may be not correct when starting name node or data node

2013-01-29 Thread Jerry Chen (JIRA)

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

Jerry Chen commented on HADOOP-9260:


Please note that I changed the hadoop version manually to Hadoop 2.0.2-alpha 
for my own testing purposes and that doesn't related to the problem.

> Hadoop version may be not correct when starting name node or data node
> --
>
> 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/ -r 1439752
> 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


[jira] [Commented] (HADOOP-9260) Hadoop version may be not correct when starting name node or data node

2013-01-29 Thread Jerry Chen (JIRA)

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

Jerry Chen commented on HADOOP-9260:


The latest trunk -r 1440286 has the same problem. 

On one machine:
[hadoop@bdpe01 tools]$ hadoop version
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}

While on another machine with the same binary:
[hadoop@bdpe02 ~]$ hadoop version
Hadoop 2.0.2-alpha
Subversion http://svn.apache.org/repos/asf/hadoop/common -r 1440286
Compiled by haifeng on 2013-01-30T18:41Z
>From source with checksum 5fab855acaace993f9bbf06ebda1fa9e


> Hadoop version may be not correct when starting name node or data node
> --
>
> 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/ -r 1439752
> 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


[jira] [Commented] (HADOOP-9260) Hadoop version may be not correct when starting name node or data node

2013-01-29 Thread Jerry Chen (JIRA)

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

Jerry Chen commented on HADOOP-9260:


Hi Chris,
The trunk revision I checked out is -r 1439752 which already include 
HADOOP-9246 (-r 1439620).
This is a different problem phenomenon. Before HADOOP-9246, the 
common-version-info.properties in hadoop-common-3.0.0-SNAPSHOT.jar is NOT 
correctly generated. But in trunk -r 1439752 (which is with HADOOP-9246) the 
common-version-info.properties in hadoop-common-3.0.0-SNAPSHOT.jar is correctly 
generated. But another common-version-info.properties with incorrect 
information was packaged to hadoop-common-3.0.0-SNAPSHOT-sources.jar which 
cause the runtime may load the incorrect file since both files are in the class 
path.

Jerry

> Hadoop version may be not correct when starting name node or data node
> --
>
> 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/ -r 1439752
> 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


[jira] [Commented] (HADOOP-9260) Hadoop version may be not correct when starting name node or data node

2013-01-29 Thread Chris Nauroth (JIRA)

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

Chris Nauroth commented on HADOOP-9260:
---

Hi, Jerry.

I expected this to be resolved by the patch on HADOOP-9246, which was committed 
on 1/28.  Can you try again with the latest trunk code, and let me know if you 
still see a problem?  You can be sure that you have the HADOOP-9246 fix if the 
pom.xml for hadoop-common and hadoop-yarn-common show that the {{version-info}} 
goal is bound to {{generate-resources}}.

Thanks!


> Hadoop version may be not correct when starting name node or data node
> --
>
> 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/ -r 1439752
> 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