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

TezQA commented on TEZ-3630:
----------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12853466/TEZ-3630.1.patch
  against master revision fc0897b.

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 2 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 3.0.1) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: 
https://builds.apache.org/job/PreCommit-TEZ-Build/2273//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2273//console

This message is automatically generated.

> Tez UI: Use DAG status for controlling auto-refresh polling.
> ------------------------------------------------------------
>
>                 Key: TEZ-3630
>                 URL: https://issues.apache.org/jira/browse/TEZ-3630
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Sreenath Somarajapuram
>            Assignee: Sreenath Somarajapuram
>         Attachments: TEZ-3630.1.patch
>
>
> Issue: UI throws error on trying to access details of a SUCCEEDED DAG in a 
> RUNNING app.
> Cause: Right now we depend on app status to control polling, and its not 
> mandatory for the AM to have details about non-running DAGs run under it. 
> Hence error is thrown on polling AM for old DAG details.
> Note:
> - Current implementation uses app status as it considers a possible case 
> where DAG could move to SUCCEEDED state and then go back to RUNNING.
> - It also presumed the AM to have data about all DAGs run under it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to