[jira] [Resolved] (MAPREDUCE-4235) Killing app can lead to inconsistent app status between RM and HS

["Jason Lowe (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MAPREDUCE-4235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Lowe resolved MAPREDUCE-4235.
-----------------------------------

    Resolution: Not A Problem

This is an inherent race between the RM and the AM.  The AM can succeed or fail *just* as the RM tries to kill it.  Whether the RM reports the job as successful or killed is based on which way the race is resolved.  In practice clients should not be surprised if a kill request ends up with the application in a non-killed terminal state such as FAILED/SUCCEEDED because of this race
                
> Killing app can lead to inconsistent app status between RM and HS
> -----------------------------------------------------------------
>
>                 Key: MAPREDUCE-4235
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4235
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.3
>            Reporter: Jason Lowe
>
> If a client tries to kill an application that is about to complete, the application states between the ResourceManager's web UI and the history server can be inconsistent.  When the problem occurs, the ResourceManager shows the Status/FinalStatus as KILLED/KILLED and the history link will redirect to a broken link.  The history link still references the ApplicationMaster which is now missing.  The history server entry will show the application state as SUCCEEDED.

--
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