Build failed in Jenkins: Hadoop-Hdfs-trunk #1102

See Changes: [harsh] Reverting MAPREDUCE-4422 from trunk until all comments are addressed [harsh] MAPREDUCE-4422. YARN_APPLICATION_CLASSPATH needs a documented default value in YarnConfiguration. Contributed by Ahmed Radwan. (harsh)

Hadoop-Hdfs-trunk - Build # 1102 - Still Failing

See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1102/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 11685 lines...] [INFO] Building jar: /home/jenkins/jenki

Re: StreamXMLRecordReader

It wasn't removed ./hadoop-tools/hadoop-streaming/src/main/java/org/apache/hadoop/streaming/S treamXmlRecordReader.java It just got mavenized and moved to a different location. And please don't cross post, hdfs-dev is not really going to help with a streaming question. --Bobby Evans On 7/12/12

[jira] [Created] (HDFS-3656) ZKFC may write a null "breadcrumb" znode

Todd Lipcon created HDFS-3656: - Summary: ZKFC may write a null "breadcrumb" znode Key: HDFS-3656 URL: https://issues.apache.org/jira/browse/HDFS-3656 Project: Hadoop HDFS Issue Type: Bug

[jira] [Created] (HDFS-3657) libhdfs: test_libhdfs_threaded should test non-recursive delete

Colin Patrick McCabe created HDFS-3657: -- Summary: libhdfs: test_libhdfs_threaded should test non-recursive delete Key: HDFS-3657 URL: https://issues.apache.org/jira/browse/HDFS-3657 Project: Hado

[jira] [Created] (HDFS-3658) TestDFSClientRetries#testNamenodeRestart failed due to MD5 mismatch

Eli Collins created HDFS-3658: - Summary: TestDFSClientRetries#testNamenodeRestart failed due to MD5 mismatch Key: HDFS-3658 URL: https://issues.apache.org/jira/browse/HDFS-3658 Project: Hadoop HDFS

[jira] [Created] (HDFS-3659) add the missed @Override to methods

Brandon Li created HDFS-3659: Summary: add the missed @Override to methods Key: HDFS-3659 URL: https://issues.apache.org/jira/browse/HDFS-3659 Project: Hadoop HDFS Issue Type: Improvement

[jira] [Created] (HDFS-3660) TestDatanodeBlockScanner#testBlockCorruptionRecoveryPolicy2 times out

Eli Collins created HDFS-3660: - Summary: TestDatanodeBlockScanner#testBlockCorruptionRecoveryPolicy2 times out Key: HDFS-3660 URL: https://issues.apache.org/jira/browse/HDFS-3660 Project: Hadoop HDFS

[jira] [Reopened] (HDFS-3568) fuse_dfs: add support for security

[ https://issues.apache.org/jira/browse/HDFS-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe reopened HDFS-3568: > fuse_dfs: add support for security > -- > >

[jira] [Resolved] (HDFS-3568) fuse_dfs: add support for security

[ https://issues.apache.org/jira/browse/HDFS-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe resolved HDFS-3568. Resolution: Fixed Re-resolving this as 'fixed' rather than 'implemented', at Harsh's

[jira] [Resolved] (HDFS-3647) Backport HDFS-2868 (Add number of active transfer threads to the DataNode status) to branch-1

[ https://issues.apache.org/jira/browse/HDFS-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-3647. --- Resolution: Fixed Fix Version/s: 1.2.0 Target Version/s: (was: 1.2.0) Hadoop Flags:

Re: HDFS mvn eclipse:eclipse not working?

No, this shouldn't ideally happen since we do check for eclipse:eclipse failures in our pre-commit builds. I am able to run it successfully on the HEAD right now, from within the directory you mention. What error are you seeing though, can you copy/paste some snippets or post a pastebin link? On

Re: HDFS mvn eclipse:eclipse not working?

Sure here's the pastebin: http://pastebin.com/ETmCNRbe On Fri, Jul 13, 2012 at 10:32 PM, Harsh J wrote: > No, this shouldn't ideally happen since we do check for > eclipse:eclipse failures in our pre-commit builds. > > I am able to run it successfully on the HEAD right now, from within > the di

Re: HDFS mvn eclipse:eclipse not working?

Your issue is cause of lack of dependencies required to build the trunk. You will need, as indicated on http://wiki.apache.org/hadoop/HowToContribute, the protobuf binaries of version 2.4 at least. Since you are on a mac, you may as well do: $ brew install protobuf And then running a build shoul