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

Naganarasimha G R commented on YARN-4044:
-----------------------------------------

Hi [~sunilg], IIUC intention of this jira is to show in the ATS UI with the 
modifed queue or priority if any right ?. If so it requires modification in 
{{ApplicationHistoryManagerOnTimelineStore.convertToApplicationReport}} needs 
to capture the event {{ApplicationMetricsConstants.UPDATED_EVENT_TYPE}} and 
update the ApplicationReport object. At the same time we need to ensure that if 
multiple application updates are done then we need to show the latest update in 
the UI. As per the logic what i  see in 
{{LeveldbTimelineStore.getEntity(String, String, Long, EnumSet<Field>, 
LeveldbIterator, byte[], int)}} seems like all the events are captured and 
returned in which case we need to check return the report with the information 
present in latest {{ApplicationMetricsConstants.UPDATED_EVENT_TYPE}} 

> Running applications information changes such as movequeue is not published 
> to TimeLine server
> ----------------------------------------------------------------------------------------------
>
>                 Key: YARN-4044
>                 URL: https://issues.apache.org/jira/browse/YARN-4044
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager, timelineserver
>    Affects Versions: 2.7.0
>            Reporter: Sunil G
>            Assignee: Sunil G
>            Priority: Critical
>         Attachments: 0001-YARN-4044.patch, 0002-YARN-4044.patch
>
>
> SystemMetricsPublisher need to expose an appUpdated api to update any change 
> for a running application.
> Events can be 
>       - change of queue for a running application.
>         - change of application priority for a running application.
> This ticket intends to handle both RM and timeline side changes. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to