You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Hitesh Shah (JIRA)" <ji...@apache.org> on 2013/04/10 21:43:16 UTC
[jira] [Created] (MAPREDUCE-5142) MR AM unregisters with state
KILLED when an error causes dispatcher to shutdown
Hitesh Shah created MAPREDUCE-5142:
--------------------------------------
Summary: MR AM unregisters with state KILLED when an error causes dispatcher to shutdown
Key: MAPREDUCE-5142
URL: https://issues.apache.org/jira/browse/MAPREDUCE-5142
Project: Hadoop Map/Reduce
Issue Type: Bug
Reporter: Hitesh Shah
RMCommunicator sets final state to KILLED if the job is in a running state and isSignalled is set to true.
{code}
} 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;
{code}
This happens when for some reason, there is an exception in a state machine's event handler causing 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira