hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Wang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-5101) YARN_APPLICATION_UPDATED event is parsed in ApplicationHistoryManagerOnTimelineStore#convertToApplicationReport with reversed order
Date Tue, 18 Oct 2016 21:56:58 GMT

     [ https://issues.apache.org/jira/browse/YARN-5101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Wang updated YARN-5101:
------------------------------
    Fix Version/s: 3.0.0-alpha2

> 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
>             Fix For: 2.8.0, 3.0.0-alpha2
>
>         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


Mime
View raw message