[
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.0001.patch
Attaching a patch addressing this issue.
As mentioned earlier, we could check for the time stamp as a reference to
identify the latest event. During appUpdate event, since we are ensuring that
all params (queue name, priority) are updated, we do not need to handle cases
like partial updates for one parameter in certain events.
[~xgong], [~rohithsharma], please help to check the patch.
> 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
>
>
> 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: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
