hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amareshwari Sriramadasu (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5473) Race condition in command-line kill for a task
Date Tue, 24 Mar 2009 06:53:50 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688589#action_12688589
] 

Amareshwari Sriramadasu commented on HADOOP-5473:
-------------------------------------------------

bq. 2. TT reports the task status as SUCCEEDED.
When TT reports task as SUCCEEDED, and there was user request to kill the task, 
1. we can accept the state as SUCCEEDED. and ignore user request to kill. (remove the request
from tasksToKill map and don't send a KillTaskAction). 
or
2. Dont accept the state as SUCCEEDED, mark it KILLED and send a KillTaskAction.

Thoughts?

> Race condition in command-line kill for a task
> ----------------------------------------------
>
>                 Key: HADOOP-5473
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5473
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Amareshwari Sriramadasu
>
> The race condition occurs in following sequence of events:
> 1. User issues a command-line kill for a RUNNING map-task. JT stores the task in tasksToKill
mapping.
> 2. TT reports the task status as SUCCEEDED.
> 3. JT creates a TaskCompletionEvent as SUCCEEDED. Also sends a killTaskAction.
> 4. Reducers fail fetching the map output.
> 5. finally, the task would fail with Fetch failures. After HADOOP-4759, the task is left
as FAILED_UNCLEAN task, since the task is present in tasksToKill mapping.

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


Mime
View raw message