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

Posted to issues@tez.apache.org by "Rajesh Balamohan (Jira)" <ji...@apache.org> on 2020/05/06 08:19:00 UTC

[jira] [Assigned] (TEZ-4171) DAGImp::getDAGStatus should try to report RUNNING state information correctly

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

Rajesh Balamohan reassigned TEZ-4171:
-------------------------------------

    Assignee: Rajesh Balamohan

> DAGImp::getDAGStatus should try to report RUNNING state information correctly
> -----------------------------------------------------------------------------
>
>                 Key: TEZ-4171
>                 URL: https://issues.apache.org/jira/browse/TEZ-4171
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Rajesh Balamohan
>            Assignee: Rajesh Balamohan
>            Priority: Major
>         Attachments: TEZ-4171.1.patch
>
>
> [https://github.com/apache/tez/blob/master/tez-dag/src/main/java/org/apache/tez/dag/app/dag/impl/DAGImpl.java#L593]
>  
> [https://github.com/apache/tez/blob/master/tez-dag/src/main/java/org/apache/tez/dag/app/dag/impl/DAGImpl.java#L953]
>  
> It is possible that the state changed to "RUNNING" and signaling was done. However, if  getDAGStatus gets invoked later, it wouldn't receive any signal and ends up waiting until the timeout. For clients trying to report details on SUBMIT–>RUNNING, it ends up giving wrong picture.
>  



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