[
https://issues.apache.org/jira/browse/MAPREDUCE-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated MAPREDUCE-3098:
-----------------------------------
Attachment: MR-3098.1.patch
Summary of changes:
- Changed ApplicationState to YarnApplicationState
- ApplicationState.SUCCEEDED is now YarnApplicationState.FINISHED.
- Changed String finalState to Enum FinalApplicationStatus
- Added an UNDEFINED final status to keep things cleaner for when the
final status has not been set by the application ( i.e. when the app is still
running )
> Report Application status as well as ApplicationMaster status in
> GetApplicationReportResponse
> ----------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3098
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3098
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Hitesh Shah
> Assignee: Hitesh Shah
> Priority: Blocker
> Fix For: 0.23.0
>
> Attachments: MR-3098.1.patch
>
>
> Currently, an application report received by the client from the RM/ASM for a
> given application returns the status of the application master. It does not
> return the status of the application i.e. whether that particular job
> succeeded or failed.
> The AM status would be one of FINISHED (SUCCEEDED should be renamed to
> FINISHED as AM state does not indicate overall success/failure), FAILED or
> KILLED.
> The final state sent by the AM to the RM in the
> FinishApplicationMasterRequest should be exposed to the client as
> ApplicationState.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
