hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3451) Add start time and end time in ApplicationAttemptReport and display the same in RMAttemptBlock WebUI
Date Fri, 10 Apr 2015 19:25:12 GMT

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

Hadoop QA commented on YARN-3451:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12724630/Screen%20Shot%202015-04-11%20at%2012.38.05%20AM.png
  against trunk revision 7660da9.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/7304//console

This message is automatically generated.

> Add start time and end time in ApplicationAttemptReport and display the same in RMAttemptBlock
WebUI
> ----------------------------------------------------------------------------------------------------
>
>                 Key: YARN-3451
>                 URL: https://issues.apache.org/jira/browse/YARN-3451
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: api, webapp
>            Reporter: Rohith
>            Assignee: Rohith
>         Attachments: 0001-YARN-3451.patch, Screen Shot 2015-04-11 at 12.38.05 AM.png
>
>
> Unlike ApplicationReport and ApplicationBlock has *Started:* and *Elapsed:* time, It
would be usefull if start time and Elapsed is sent in ApplicationAttemptReport and display
in ApplicationAttemptBlock. 
> This gives granular debugging ability when analyzing issue with multiple attempt failure
like attempt timedout.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message