tez-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] (TEZ-1967) Add a monitoring API on DAGClient which returns after a time interval or on DAG state change
Date Thu, 26 Feb 2015 17:05:04 GMT

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

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

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

    {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: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
2.0.3) 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/233//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/233//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
>         Attachments: TEZ-1967-InitialReview.patch, TEZ-1967.1.patch, TEZ-1967.2.patch,
TEZ-1967.3.patch, TEZ-1967.4.patch, TEZ-1967.5.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)

Mime
View raw message