You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tez.apache.org by "László Bodor (Jira)" <ji...@apache.org> on 2020/08/25 14:59:05 UTC

[jira] [Updated] (TEZ-4146) Register RUNNING state in DAG's state change callback

     [ https://issues.apache.org/jira/browse/TEZ-4146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

László Bodor updated TEZ-4146:
------------------------------
    Fix Version/s: 0.10.0

> Register RUNNING state in DAG's state change callback
> -----------------------------------------------------
>
>                 Key: TEZ-4146
>                 URL: https://issues.apache.org/jira/browse/TEZ-4146
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Rajesh Balamohan
>            Assignee: Rajesh Balamohan
>            Priority: Minor
>             Fix For: 0.10.0, 0.10.1, 0.9.3
>
>         Attachments: TEZ-4146.1.patch, TEZ-4146.2.patch, TEZ-4146.3.patch
>
>
> It would be good to register RUNNING in the DAG state change callbacks. This would help applications like Hive, when it [monitors the job|https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/exec/tez/monitoring/TezJobMonitor.java#L182] continuously for getting runtime breakdown at the end of the job..



--
This message was sent by Atlassian Jira
(v8.3.4#803005)