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 03:18:12 UTC
[jira] [Commented] (YARN-5100) The YarnApplicationState is always
running in ATS no matter the application is running or finishes.
[ https://issues.apache.org/jira/browse/YARN-5100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15285943#comment-15285943 ]
Xuan Gong commented on YARN-5100:
---------------------------------
We should parse the events in reversed order. Applied a fix.
> The YarnApplicationState is always running in ATS no matter the application is running or finishes.
> ---------------------------------------------------------------------------------------------------
>
> Key: YARN-5100
> URL: https://issues.apache.org/jira/browse/YARN-5100
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.8.0
> Reporter: Xuan Gong
> Assignee: Xuan Gong
> Priority: Blocker
> Attachments: YARN-5100.1.patch
>
>
> After YARN-5029, we add one more event : APP_STATE_UPDATE event which is used by RM to sync up the App state between Timeline Server. But when we get appReport from TimelineServer, we parse all events with timestamp descending order (Finish event-->App State update event --> create event) which causes this issue.
--
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