You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Amareshwari Sri Ramadasu (JIRA)" <ji...@apache.org> on 2007/10/23 11:34:50 UTC
[jira] Updated: (HADOOP-1893) Exception thrown from pipes Map task
is not handled properly
[ https://issues.apache.org/jira/browse/HADOOP-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amareshwari Sri Ramadasu updated HADOOP-1893:
---------------------------------------------
Fix Version/s: 0.16.0
Description:
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.
was:
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.
Affects Version/s: (was: 0.15.0)
> Exception thrown from pipes Map task is not handled properly
> ------------------------------------------------------------
>
> Key: HADOOP-1893
> URL: https://issues.apache.org/jira/browse/HADOOP-1893
> Project: Hadoop
> Issue Type: Bug
> Components: pipes
> Reporter: Amareshwari Sri Ramadasu
> Fix For: 0.16.0
>
>
> 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.