[jira] Resolved: (MAPREDUCE-77) JobConf is deprecated but Job does not support a constructor for Configuration

[ https://issues.apache.org/jira/browse/MAPREDUCE-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amareshwari Sriramadasu resolved MAPREDUCE-77. -- Resolution: Invalid Now that JobControl is modified to use new api, y

[jira] Resolved: (MAPREDUCE-67) Few tasks failed while creating the work directory for a job, when job tracker was restarted

[ https://issues.apache.org/jira/browse/MAPREDUCE-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amareshwari Sriramadasu resolved MAPREDUCE-67. -- Resolution: Invalid That was a cluster configuration issue. > Few ta

Job vs. Configuration

Hey all Looking at (converting to) the new .20 API, I see that the static config setters take Job or JobContext, not Configuration. >> public static Path[] getInputPaths(JobContext context) I get the utility of this from the perspective of a user writing hadoop jobs. a lot less job.getConf

Re: Question: how to run hadoop after the project split?

Hi Philip, Tried the script. It seems that the script could start a cluster but the web page did not work. Got the following error from the web interface: HTTP ERROR: 404 /dfshealth.jsp RequestURI=/dfshealth.jsp Powered by Jetty:// Thanks, Nicholas - Original Message > From: Phili

Re: Question: how to run hadoop after the project split?

FWIW, I've been using the following simple shell script: [0]doorstop:hadoop(149128)$cat damnit.sh #!/bin/bash set -o errexit set -x cd hadoop-common ant binary cd .. cd hadoop-hdfs ant binary cd .. cd hadoop-mapreduce ant binary cd .. mkdir -p all/bin all/lib all/contrib cp hadoop-common/bin/*

Re: Question: how to run hadoop after the project split?

Hi Todd, Two problems: - The patch in HADOOP-6152 cannot be applied. - I have tried an approach similar to the one described by the slides but it did not work since jetty cannot find the webapps directory. See below: 2009-08-10 17:54:41,671 WARN org.mortbay.log: Web application not found file:

Re: Question: how to run hadoop after the project split?

I'd hazard a guess and say we should hitch our wagon to https://issues.apache.org/jira/browse/HADOOP-5107 . Arun On Aug 10, 2009, at 5:25 PM, Tsz Wo (Nicholas), Sze wrote: I have to admit that I don't know the official answer. The hack below seems working: - compile all 3 sub-projects; - c

Question: how to run hadoop after the project split?

I have to admit that I don't know the official answer. The hack below seems working: - compile all 3 sub-projects; - copy everything in hdfs/build and mapreduce/build to common/build; - then run hadoop by the scripts in common/bin as before. Any better idea? Nicholas Sze

[jira] Created: (MAPREDUCE-845) build.xml

build.xml - Key: MAPREDUCE-845 URL: https://issues.apache.org/jira/browse/MAPREDUCE-845 Project: Hadoop Map/Reduce Issue Type: Bug Components: build Affects Versions: 0.21.0 Environment: building on RHEL5 with

Build failed in Hudson: Hadoop-Mapreduce-trunk #44

See http://hudson.zones.apache.org/hudson/job/Hadoop-Mapreduce-trunk/44/changes Changes: [sharad] MAPREDUCE-814. Provide a way to configure completed job history files to be on HDFS. -- [...truncated 130729 lines...] [junit] 2009-08-10 18:16:41,166 IN

[jira] Created: (MAPREDUCE-844) TestJobTrackerRestartWithLostTracker fails sometimes

TestJobTrackerRestartWithLostTracker fails sometimes Key: MAPREDUCE-844 URL: https://issues.apache.org/jira/browse/MAPREDUCE-844 Project: Hadoop Map/Reduce Issue Type: Bug Repo

[jira] Created: (MAPREDUCE-843) Cleanup JobInProgress

Cleanup JobInProgress -- Key: MAPREDUCE-843 URL: https://issues.apache.org/jira/browse/MAPREDUCE-843 Project: Hadoop Map/Reduce Issue Type: Improvement Components: jobtracker Reporter: Amar Kamat

[jira] Resolved: (MAPREDUCE-720) Task logs should have right access-control

[ https://issues.apache.org/jira/browse/MAPREDUCE-720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod K V resolved MAPREDUCE-720. - Resolution: Duplicate The latest approach slated at HADOOP-4491 invalidates this JIRA issue.