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

Hadoop QA commented on YARN-5100:
---------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s 
{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} docker {color} | {color:red} 5m 57s 
{color} | {color:red} Docker failed to build yetus/hadoop:2c91fd8. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12804330/YARN-5100.1.patch |
| JIRA Issue | YARN-5100 |
| Console output | 
https://builds.apache.org/job/PreCommit-YARN-Build/11491/console |
| Powered by | Apache Yetus 0.2.0   http://yetus.apache.org |


This message was automatically generated.



> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to