Hi,
Well I've figured some of it out. I needed to initialise the new
JobClient after setting its configuration. So the code looks like:
JobClient aJC = new JobClient();
String jobid = jobConf.get("mapred.job.id");
aJC.setConf(jobConf);
aJC.init();
This works fine in the Map function for killing
Hi Michael,
Thanks for the reply. I've tried to write some code to do this now but
its not working. I was wondering if there's anything obviously wrong?
After my runJob() I put (just as a test):
JobClient aJC = new JobClient();
String jobid = jobConf.get("mapred.job.id");
aJC.setConf(jobConf
On 8/2/07 5:20 AM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> I've found the
> getMapTaskReports method in the JobClient class, but can't work out
> how to access it other than by creating a new instance of JobClient -
> but then that JobClient would be a differnt one to the one that was
Hi Doug,
Thanks for the reply. Could you possibly explain how my program would
get access to the task reports from each tracker? I've found the
getMapTaskReports method in the JobClient class, but can't work out
how to access it other than by creating a new instance of JobClient -
but the
[EMAIL PROTECTED] wrote:
I've written a map task that will on occasion not compute the correct
result. This can easily be detected, at which point I'd like the map
task to report the error and terminate the entire map/reduce job. Does
anyone know of a way I can do this?
You can easily kill th
Well, I don't think it will be too much of a problem for me. I'll only
be running this one type of job. The problem I have is that I can only
throw IOExceptions out of the Mapper function. So if a job fails for
some other reason, other than my numerical calculation error I have no
way of kn
Hi,
On 7/30/07, Anthony D. Urso <[EMAIL PROTECTED]> wrote:
> Call JobConf.setMaxMapAttempts(0) in the job conf, then throw an exception
> when your mapper fails. This should kill the entire job instantly, since
> the job tracker will allow no mapper failures.
Wouldn't this cause all other runnin
In that case, it would be better to communicate the error in-band somehow
before throwing the exception.
On Tue, Jul 31, 2007 at 12:09:27AM +0100, [EMAIL PROTECTED] wrote:
> Thanks Anthony, its good to know it can be done! However, I was hoping
> to be able to report the numerical error in my ma
Thanks Anthony, its good to know it can be done! However, I was hoping
to be able to report the numerical error in my map function. With the
the way you suggest would there be any way to access the exception
thrown? I'm running the map-reduce job from a gui, so would rather
have an error bo
Call JobConf.setMaxMapAttempts(0) in the job conf, then throw an exception
when your mapper fails. This should kill the entire job instantly, since
the job tracker will allow no mapper failures.
Cheers,
Anthony
On Mon, Jul 30, 2007 at 09:42:09PM +0100, [EMAIL PROTECTED] wrote:
> Hi,
>
> Apolog
Hi,
Apologies for yet another question from me, but here goes!
I've written a map task that will on occasion not compute the correct
result. This can easily be detected, at which point I'd like the map
task to report the error and terminate the entire map/reduce job. Does
anyone know of a
11 matches
Mail list logo
