Hello,
I have given a case where my mapper should fail. That is, based on a
result it throws an exception
if(res==0) throw new IOException("Error in code!, see stderr/out");
,
When i go to the JobTracker website, e.g
http://tracker.com:50030/jobdetails.jsp?jobid=job_200903051709_0024&refresh=30
and click on one of the running tasks, I see an IOException in the
errors column.
But on the jobtracker page for the job, it doesn't fail - it stays in
the running column , never moving to the failed/killed columns (not
even after 10 minutes)

Why so?
Regards
Saptarshi Guha

Is your job a streaming job?
If so, Which version of hadoop are you using? what is the configured
value for stream.non.zero.exit.is.failure? Can you see
stream.non.zero.exit.is.failure to true and try again?
Thanks
Amareshwari
Saptarshi Guha wrote:
> Hello,
> I have given a case where my mapper should fail. That is, based on a
> result it throws an exception
> if(res==0) throw new IOException("Error in code!, see stderr/out");
> ,
> When i go to the JobTracker website, e.g
> http://tracker.com:50030/jobdetails.jsp?jobid=job_200903051709_0024&refresh=30
> and click on one of the running tasks, I see an IOException in the
> errors column.
> But on the jobtracker page for the job, it doesn't fail - it stays in
> the running column , never moving to the failed/killed columns (not
> even after 10 minutes)
>
> Why so?
> Regards
>
>
> Saptarshi Guha
>

Just trying to understand this better, are you observing that the task,
which failed with the IOException, not getting marked as killed? If yes,
that does not look right...

Jothi

On 3/6/09 8:12 AM, "Saptarshi Guha" <[EMAIL PROTECTED]> wrote:

> Hello,
> I have given a case where my mapper should fail. That is, based on a
> result it throws an exception
> if(res==0) throw new IOException("Error in code!, see stderr/out");
> ,
> When i go to the JobTracker website, e.g
> http://tracker.com:50030/jobdetails.jsp?jobid=job_200903051709_0024&refresh=30
> and click on one of the running tasks, I see an IOException in the
> errors column.
> But on the jobtracker page for the job, it doesn't fail - it stays in
> the running column , never moving to the failed/killed columns (not
> even after 10 minutes)
>
> Why so?
> Regards
>
>
> Saptarshi Guha

I meant, "not marked as failed" ...
On 3/6/09 10:37 AM, "Jothi Padmanabhan" <[EMAIL PROTECTED]> wrote:

> Just trying to understand this better, are you observing that the task, which
> failed with the IOException, not getting marked as killed? If yes, that does
> not look right...
>
> Jothi
>
> On 3/6/09 8:12 AM, "Saptarshi Guha" <[EMAIL PROTECTED]> wrote:
>
>> Hello,
>> I have given a case where my mapper should fail. That is, based on a
>> result it throws an exception
>> if(res==0) throw new IOException("Error in code!, see stderr/out");
>> ,
>> When i go to the JobTracker website, e.g
>>
http://tracker.com:50030/jobdetails.jsp?jobid=job_200903051709_0024&refresh=3>>
0
>> and click on one of the running tasks, I see an IOException in the
>> errors column.
>> But on the jobtracker page for the job, it doesn't fail - it stays in
>> the running column , never moving to the failed/killed columns (not
>> even after 10 minutes)
>>
>> Why so?
>> Regards
>>
>>
>> Saptarshi Guha