[
https://issues.apache.org/jira/browse/YARN-5101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sunil G updated YARN-5101:
--------------------------
Attachment: YARN-5101.0002.patch
Thanks [~rohithsharma]. It makes sense.
Updated a patch with this approach, however {{SystemClock}} was used by
{{RMAppImpl}} which is internally using {{System.currentTimeMillis}} and it was
available only in RMAppImpl, so CS#updateApplicationPriority had to use old
approach. I will raise a separate jira to use MonotonicClock for RMAppImpl.
> YARN_APPLICATION_UPDATED event is parsed in
> ApplicationHistoryManagerOnTimelineStore#convertToApplicationReport with
> reversed order
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: YARN-5101
> URL: https://issues.apache.org/jira/browse/YARN-5101
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.8.0
> Reporter: Xuan Gong
> Assignee: Sunil G
> Attachments: YARN-5101.0001.patch, YARN-5101.0002.patch
>
>
> Right now, the application events are parsed in in
> ApplicationHistoryManagerOnTimelineStore#convertToApplicationReport with
> timestamp descending order, which means the later events would be parsed
> first, and the previous same type of events would override the information. In
> https://issues.apache.org/jira/browse/YARN-4044, we have introduced
> YARN_APPLICATION_UPDATED events which might be submitted by RM multiple times
> in one application life cycle. This could cause problem.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
