[jira] [Commented] (TEZ-1631) Session dag submission timeout can result in duplicate DAG submissions

["Jeff Zhang (JIRA)" <ji...@apache.org>]

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

Jeff Zhang commented on TEZ-1631:
---------------------------------

[~bikassaha]  I attach the patch based on branch-0.4.1-incubating.  Just move checking SubmissionTimedOut before modifying DAG. 

> Session dag submission timeout can result in duplicate DAG submissions
> ----------------------------------------------------------------------
>
>                 Key: TEZ-1631
>                 URL: https://issues.apache.org/jira/browse/TEZ-1631
>             Project: Apache Tez
>          Issue Type: Bug
>    Affects Versions: 0.4.1
>            Reporter: Bikas Saha
>         Attachments: Tez-1631.patch
>
>
> In TezSession.submitDAG() we could first check if the session is ready and throw a SessionNotRunning exception if that is not the case. This should be done before processing the DAG and thus will prevent unnecessary modification of the DAG.
> If the session is ready then we can submit the DAG as usual. Higher level components already handle SessionNotRunning exception.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)