Re: Error reporting from map function

Hi,

On 7/30/07, Anthony D. Urso <anthonyu@...> 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 running and future jobs to stop
attempting to recover from an error? Or do all jobs have copies of the
original job conf?

--

regards,

Jeroen