hadoop-mapreduce-issues mailing list archives

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

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

Hadoop QA commented on MAPREDUCE-5835:

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
1.3.9) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4510//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4510//console

This message is automatically generated.

> 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

View raw message