[jira] [Resolved] (HADOOP-8546) missing hdfs user guide and command pages from hadoop project page
[ https://issues.apache.org/jira/browse/HADOOP-8546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins resolved HADOOP-8546. - Resolution: Duplicate Per HDFS-3458 the forest docs needed to be ported to APT. missing hdfs user guide and command pages from hadoop project page Key: HADOOP-8546 URL: https://issues.apache.org/jira/browse/HADOOP-8546 Project: Hadoop Common Issue Type: Improvement Reporter: Jason Shih Priority: Trivial cant find the web master contact thus file issue in jira. two of the following links are missing from hadoop project page, maybe you can help restoring back them. thanks http://hadoop.apache.org/common/docs/current/hadoop-project-dist/hadoop-hdfs/hdfs_user_guide.html http://hadoop.apache.org/common/docs/current/hadoop-project-dist/hadoop-common/commands_manual.html Cheers, Jason -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HADOOP-8548) test-patch.sh shows an incorrect link in Jekins builds
Kihwal Lee created HADOOP-8548: -- Summary: test-patch.sh shows an incorrect link in Jekins builds Key: HADOOP-8548 URL: https://issues.apache.org/jira/browse/HADOOP-8548 Project: Hadoop Common Issue Type: Bug Components: build Reporter: Kihwal Lee Precommit builds show an incorrect link for javac warnings. {noformat} Javac warnings: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2539//artifact/trunk/trunk/patchprocess/diffJavacWarnings.txt {noformat} Note that 'trunk' appears twice. Do we need $(basename $BASEDIR) in the following? Other places don't have it. {code:title=test-patch.sh} JIRA_COMMENT_FOOTER=Javac warnings: $BUILD_URL/artifact/trunk/$(basename $BASEDIR)/patchprocess/diffJavacWarnings.txt {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HADOOP-8534) Some tests leave a config file open causing failure on windows
[ https://issues.apache.org/jira/browse/HADOOP-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Radia resolved HADOOP-8534. -- Resolution: Fixed Committed to Hadoop-1 windows branch. Thanks Ivan. Some tests leave a config file open causing failure on windows -- Key: HADOOP-8534 URL: https://issues.apache.org/jira/browse/HADOOP-8534 Project: Hadoop Common Issue Type: Bug Components: conf Affects Versions: 1.0.0 Reporter: Ivan Mitic Assignee: Ivan Mitic Attachments: HADOOP-8534-branch-1-win_Parser(2).patch, HADOOP-8534-branch-1-win_Parser.patch Java xml parser keeps file locked after SAXException, causing the following tests to fail: - TestQueueManagerForJobKillAndJobPriority - TestQueueManagerForJobKillAndNonDefaultQueue {{TestQueueManagerForJobKillAndJobPriority#testQueueAclRefreshWithInvalidConfFile()}} is creating a temp config file with incorrect syntax. Later, the test tries to delete/cleanup this file and this operation fails on Windows (as the file is still open). From this point on, all subsequent tests fail because they try to use the incorrect config file. Forum references on the problem and the fix: http://www.linuxquestions.org/questions/programming-9/java-xml-parser-keeps-file-locked-after-saxexception-768613/ https://forums.oracle.com/forums/thread.jspa?threadID=2046505start=0tstart=0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Doubt regarding debugging Hadoop Classes
As far as I can tell, the Fetcher class executes from within a Task JVM. So check your reduce's userlogs output instead of the service's/daemon's logs. Additionally, depending on what version of Hadoop you're using for your project, try this: http://search-hadoop.com/m/SKajPZOkJa1 On Tue, Jul 3, 2012 at 4:29 AM, Pavan Kulkarni pavan.babu...@gmail.com wrote: Hi, I am new to Hadoop community and am working on a project which involves tweaking few Hadoop classes. To enable debugging for a certain class (say Fetcher.java) I inserted a line *log4j.logger.org.apache.hadoop.mapreduce.task.reduce.Fetcher=DEBUG* * * Then I restarted the daemon's and grep'd in the log directory for the Debug message present in the Fetcher.java class. I couldn't find any !! Am I missing anything here? Any help is highly appreciated .Thanks -- --With Regards Pavan Kulkarni -- Harsh J
Re: PreCommit-Admin not running
Move to dev alias, it seems to stop working since weekend. Thanks, Junping - Original Message - From: Kihwal Lee kih...@yahoo-inc.com To: gene...@hadoop.apache.org Sent: Tuesday, July 3, 2012 3:59:28 AM Subject: PreCommit-Admin not running It looks like the PreCommit-Admin build job is not running. Can anyone give it a gentle nudge? Kihwal