Rohith Sharma K S commented on YARN-3543:

bq. I think we should also update TimelineServer.md to describe this and update 
the example.
make sense, and I find ResourceManagerRest.md also need to update. And there 
are new fields to be udpated in doc which I raise separe issue for general doc 
udpate. Current patch updates ResourceManagerRest.md for new field added by 
this patch.

bq. Looks like that we will not use RMApplicationHistoryWriter anymore, 
probably we can undo the related changes ?
Given ApplicationHistoryService is not used, it can be removed. I see that it 
is no more used, so will remove this.

> ApplicationReport should be able to tell whether the Application is AM 
> managed or not. 
> ---------------------------------------------------------------------------------------
>                 Key: YARN-3543
>                 URL: https://issues.apache.org/jira/browse/YARN-3543
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: api
>    Affects Versions: 2.6.0
>            Reporter: Spandan Dutta
>            Assignee: Rohith Sharma K S
>         Attachments: 0001-YARN-3543.patch, 0001-YARN-3543.patch, 
> 0002-YARN-3543.patch, 0002-YARN-3543.patch, 0003-YARN-3543.patch, 
> 0004-YARN-3543.patch, 0004-YARN-3543.patch, 0004-YARN-3543.patch, 
> 0005-YARN-3543.patch, YARN-3543-AH.PNG, YARN-3543-RM.PNG
> Currently we can know whether the application submitted by the user is AM 
> managed from the applicationSubmissionContext. This can be only done  at the 
> time when the user submits the job. We should have access to this info from 
> the ApplicationReport as well so that we can check whether an app is AM 
> managed or not anytime.

This message was sent by Atlassian JIRA

Reply via email to