[
https://issues.apache.org/jira/browse/YARN-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729444#comment-14729444
]
Naganarasimha G R commented on YARN-4044:
-----------------------------------------
[~sunilg], As per the offline discussion we had, currently you are populating
the entityInfo Object with the modified priority or the queue because of which
ATS is able to provide the updated info. So yes both of my queries gets
answered with it . But one point which i can think of here is would it be
better to capture the modified priority and queue (if any) as part of eventInfo
? so that initial submission information as well as modification information
will be captured which might be helpful later in analysis.
> 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)
