hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Roelofs (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-384) Exception thrown from pipes Map task is not handled properly
Date Sat, 02 Oct 2010 03:50:32 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12917152#action_12917152

Greg Roelofs commented on MAPREDUCE-384:

This has been sitting here for three years--do you know if it's still an issue?  If so, I'll
see if we can get it into the queue for 0.22.

> Exception thrown from pipes Map task is not handled properly
> ------------------------------------------------------------
>                 Key: MAPREDUCE-384
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-384
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: pipes
>            Reporter: Amareshwari Sriramadasu
>   In Pipes environment, when map task throws an exception it is not killed immediately.
But the tracker is waiting for 603 seconds (10 mins) for the report and then killing the task.
> When I threw exception from word count sample program the maptask exits after 603 seconds
showing the following on console:
> 07/09/14 11:09:26 INFO mapred.JobClient: Task Id : task_200709141017_0002_m_000001_1,
Status : FAILED
> task_200709141017_0002_m_000001_1: terminate called after throwing an instance of 'std::exception'
> task_200709141017_0002_m_000001_1:   what():  St9exception
> And the Job UI shows:
> Task task_200709141017_0002_m_000001_1 failed to report status for 603 seconds. Killing!
> Thus, each map task is taking  10 mins for exiting and  is tried 4 times.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message