hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gera Shegalov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5835) Killing Task might cause the job to go to ERROR state
Date Tue, 15 Apr 2014 17:33:16 GMT

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

Gera Shegalov commented on MAPREDUCE-5835:
------------------------------------------

We should run some temporal logic model checker like spin on these state machines to get rid
of this kind of issues.

> Killing Task might cause the job to go to ERROR state
> -----------------------------------------------------
>
>                 Key: MAPREDUCE-5835
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5835
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 2.4.0
>            Reporter: Ming Ma
>            Assignee: Ming Ma
>            Priority: Critical
>         Attachments: MAPREDUCE-5835.patch
>
>
> There could be a race condition if job is killed right after task attempt receives TA_DONE
event. In that case, TaskImpl might receive T_ATTEMPT_SUCCEEDED followed by T_ATTEMPTED_KILLED
for the same attempt, thus transition job to ERROR state.
> a. The task is in KILL_WAIT.
> b. TA receives TA_DONE event.
> c. Before TA transitions to SUCCEEDED state, Task sends TA_KILL event.
> d. TA transitions to SUCCEEDED state and thus send T_ATTEMPT_SUCCEEDED to the task. The
task transitions to KILLED state.
> e. TA processes TA_KILL event and sends T_ATTEMPT_KILLED to the task.
> f. When task is in KILLED state, it can't handle T_ATTEMPT_KILLED event, thus transition
job to ERROR state.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message