You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Ming Ma (JIRA)" <ji...@apache.org> on 2014/03/04 19:55:20 UTC
[jira] [Created] (MAPREDUCE-5776) TaskAttempt should honor TA_KILL
event when TA is in SUCCESS_CONTAINER_CLEANUP state
Ming Ma created MAPREDUCE-5776:
----------------------------------
Summary: TaskAttempt should honor TA_KILL event when TA is in SUCCESS_CONTAINER_CLEANUP state
Key: MAPREDUCE-5776
URL: https://issues.apache.org/jira/browse/MAPREDUCE-5776
Project: Hadoop Map/Reduce
Issue Type: Bug
Reporter: Ming Ma
In most states that a TaskAttempt goes through, such as ASSIGNED, RUNNING, SUCCEEDED etc. If a TA receives TA_KILL, the state will transit to KILLED (if the TA is in SUCCEEDED state, it depends on if it is a reducer task).
However, If the TA is in SUCCESS_CONTAINER_CLEANUP state, TA just ignores TA_KILL. Later on, SUCCESS_CONTAINER_CLEANUP will move to SUCCEEDED state after the container is cleaned up. So it is possible after a client issue a kill request, the TA will eventually be in SUCCEEDED state. It isn't a major issue. But from consistency's point of view, it is better if TA_KILL is handled in a similar way as how it is handled when TA is in SUCCEEDED state.
--
This message was sent by Atlassian JIRA
(v6.2#6252)