[MAPREDUCE-5142] MR AM unregisters with state KILLED when an error causes dispatcher to shutdown

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.0.3-alpha, 0.23.5
• Assignee: Unassigned
• Reporter: Hitesh Shah
• Created: 10/Apr/13 19:42
• Updated: 10/Apr/13 20:04

Description

RMCommunicator sets final state to KILLED if the job is in a running state and isSignalled is set to true.

      } else if (jobImpl.getInternalState() == JobStateInternal.KILLED
          || (jobImpl.getInternalState() == JobStateInternal.RUNNING && isSignalled)) {
        finishState = FinalApplicationStatus.KILLED;
      } else if (jobImpl.getInternalState() == JobStateInternal.FAILED
          || jobImpl.getInternalState() == JobStateInternal.ERROR) {
        finishState = FinalApplicationStatus.FAILED;

This happens when any uncaught exception in any event handler ends up causing the AsyncDispatcher to trigger a shutdown. In such a scenario, even though the AM actually failed due to some error, its actual state ends up as KILLED.