[ https://issues.apache.org/jira/browse/TEZ-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17102598#comment-17102598 ]
Rajesh Balamohan commented on TEZ-4171: --------------------------------------- Thanks [~gopalv] , [~jeagles] . Yes, SUBMITTED–>RUNNING transition is tracked so that clients get to know about at least in next rpc call without delay. I will create a follow up Jira to reduce lock optimization. > 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, TEZ-4171.2.patch, TEZ-4171.3.patch, > TEZ-4171.4.patch, TEZ-4171.5.patch, TEZ-4171.6.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)