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 "Xuan Gong (JIRA)" <ji...@apache.org> on 2016/05/17 17:14:12 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15287031#comment-15287031 ]
Xuan Gong commented on YARN-5101:
---------------------------------
[~sunilg] [~rohithsharma]
Could you take a look at this, please ?
> 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
>
> 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