[
https://issues.apache.org/jira/browse/MAPREDUCE-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13108381#comment-13108381
]
Vinod Kumar Vavilapalli commented on MAPREDUCE-2892:
----------------------------------------------------
We differentiate ApplicationState from the final state of the framework's AM.
For e.g., Job Kill is handled by MR AM and from the platform point of view, the
Application has simply finished, not killed. In this case, we will have
Application.State as FINISHED, with the auxiliary information of
Framework.State to be KILLED. Each framework can have arbitrary final state,
like say ABORTED.
Today, we call Framework.State as finalState, may be we should name it better.
I saw that in MAPREDUCE-3017, when an application finishes, you used the
Application.State column for printing the Framework.State when the application
finishes. IMO, we need a separate column for Framework.State.
> Improvements to AM apis
> -----------------------
>
> Key: MAPREDUCE-2892
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2892
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: mr-am, mrv2, resourcemanager
> Affects Versions: 0.23.0
> Reporter: Arun C Murthy
> Priority: Blocker
> Fix For: 0.23.0
>
>
> Some api changes before we declare yarn apis as stable:
> # FinishApplicationMasterRequest doesn't need to send out 'tracking url'.
> # FinishApplicationMasterRequest shouldn't use 'string' as final state - it's
> got to be an enum and we need to use that enum appropriately in the RM's
> state-machines.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
