You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2015/01/18 19:22:34 UTC

[jira] [Commented] (TEZ-1967) Add a monitoring API on DAGClient which returns after a time interval or on DAG state change

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

Hadoop QA commented on TEZ-1967:
--------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  http://issues.apache.org/jira/secure/attachment/12692979/TEZ-1967.1.patch
  against master revision c684653.

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

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

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

    {color:red}-1 javadoc{color}.  The javadoc tool appears to have generated 1 warning messages.
        See https://builds.apache.org/job/PreCommit-TEZ-Build/50//artifact/patchprocess/diffJavadocWarnings.txt for details.

    {color:red}-1 findbugs{color}.  The patch appears to introduce 64 new Findbugs (version 2.0.3) warnings.

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

    {color:red}-1 core tests{color}.  The patch failed these unit tests in :
                   org.apache.tez.mapreduce.TestMRRJobs

Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/50//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-TEZ-Build/50//artifact/patchprocess/newPatchFindbugsWarningstez-mapreduce.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-TEZ-Build/50//artifact/patchprocess/newPatchFindbugsWarningstez-dag.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-TEZ-Build/50//artifact/patchprocess/newPatchFindbugsWarningstez-examples.html
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/50//console

This message is automatically generated.

> Add a monitoring API on DAGClient which returns after a time interval or on DAG state change
> --------------------------------------------------------------------------------------------
>
>                 Key: TEZ-1967
>                 URL: https://issues.apache.org/jira/browse/TEZ-1967
>             Project: Apache Tez
>          Issue Type: Improvement
>    Affects Versions: 0.7.0
>            Reporter: Siddharth Seth
>            Assignee: Vasanth kumar RJ
>             Fix For: 0.7.0
>
>         Attachments: TEZ-1967.1.patch
>
>
> To monitor a running DAG, clients end up using DAGClient.getDAGSstatus in a loop with a poll interval.
> In the worst case, they find out about DAG completion, failure etc only after the poll interval.
> Instead, an API can be added which waits on the AM for a specified interval, but can return earlier if the DAG state changes.
> This will end up blocking RPC handlers - but that isn't a problem since we don't have many entities querying for DAG status.



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