[
https://issues.apache.org/jira/browse/TEZ-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasanth kumar RJ updated TEZ-1967:
----------------------------------
Attachment: TEZ-1967.2.patch
[~sseth], Implemented your review comments and attached patch.
At client side, RPC or AM call will be made once the RM says running. When RM
says running then we have to wait till AM return some DAG status. When client
side does not reaches timeout, then rest of the timeout time given to AM.
> 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-InitialReview.patch, TEZ-1967.1.patch,
> TEZ-1967.2.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)
