[ 
https://issues.apache.org/jira/browse/MAPREDUCE-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116145#comment-13116145
 ] 

Arun C Murthy commented on MAPREDUCE-3098:
------------------------------------------

bq. Apologies if I am giving an impression of creating a storm. But honestly 
all of this was thought through earlier end-to-end and I firmly belive that the 
current states and records represent the correct abstraction.

Healthy back & forth is good. Helps everyone - don't worry about it.

Seems to me that there are 2 states:
a) State of the AM _attempt_
b) State of the application itself.

Oh, we also have 'diagnostics', more on this later.

So, the crux is: forcing application writers to come up with Strings to 
describe their state seems a poor api/abstraction.

Can we do better?
                
> 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
>
>
> 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

        

Reply via email to