You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Rohith Sharma K S (JIRA)" <ji...@apache.org> on 2016/10/06 08:38:20 UTC
[jira] [Updated] (YARN-5101) YARN_APPLICATION_UPDATED event is
parsed in
ApplicationHistoryManagerOnTimelineStore#convertToApplicationReport with
reversed order
[ https://issues.apache.org/jira/browse/YARN-5101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rohith Sharma K S updated YARN-5101:
------------------------------------
Target Version/s: 2.8.0
> 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: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org