hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5100) The YarnApplicationState is always running in ATS no matter the application is running or finishes.
Date Thu, 19 May 2016 17:30:13 GMT

    [ https://issues.apache.org/jira/browse/YARN-5100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15291596#comment-15291596
] 

Hudson commented on YARN-5100:
------------------------------

SUCCESS: Integrated in Hadoop-trunk-Commit #9824 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/9824/])
YARN-5100. The YarnApplicationState is always running in ATS even (junping_du: rev 141873ca7d68619e3458712b17aed57fec8fd7c8)
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/TestApplicationHistoryManagerOnTimelineStore.java
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/ApplicationHistoryManagerOnTimelineStore.java


> 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
>             Fix For: 2.8.0
>
>         Attachments: YARN-5100.1.patch, YARN-5100.2.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


Mime
View raw message