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

Vinod Kumar Vavilapalli commented on MAPREDUCE-3098:
----------------------------------------------------

Hitesh, I think there is a confusion in the terminology in this one.

Application: YARN(RM+NM) concept. An Application is more than an AM. All the 
attempts of an AM form the application.
Job: MR concept

We never expose a single AM's state (which is different from the Job's state) 
to the client, instead we expose the overall ApplicationState (a mirror or 
RMAppState).

The ApplicationState returned to the client via ApplicationReport is really the 
state of the application as known to RM.

The final state sent by the AM to the RM is the JobState. I agree with the 
premise of this ticket that we should expose these two separately on the 
client, but we've to note that JobState doesn't have any bearing on the state 
of the application. We are routing it to the the client through RM as we don't 
have any other way. That is why I was arguing at MAPREDUCE-2892 for a binary 
blob for this JobState piped through RM. What do you think?
                
> 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