Hadoop Map/Reduce
  1. Hadoop Map/Reduce
  2. MAPREDUCE-5776

Improve TaskAttempt's handling of TA_KILL event when TA is in SUCCESS_CONTAINER_CLEANUP state

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      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.

        Activity

        Ming Ma made changes -
        Field Original Value New Value
        Summary TaskAttempt should honor TA_KILL event when TA is in SUCCESS_CONTAINER_CLEANUP state Improve TaskAttempt's handling of TA_KILL event when TA is in SUCCESS_CONTAINER_CLEANUP state
        Ming Ma created issue -

          People

          • Assignee:
            Unassigned
            Reporter:
            Ming Ma
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:

              Development