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

["Bikas Saha (JIRA)" <ji...@apache.org>]

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

Bikas Saha edited comment on TEZ-1631 at 10/1/14 12:52 AM:
-----------------------------------------------------------

Attaching patch with minor changes to fix typo in name and add tezSession.stop() in the test.


was (Author: bikassaha):
Attaching patch with minor changes.

> 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
>            Assignee: Jeff Zhang
>         Attachments: TEZ-1631.5.patch, Tez-1631-2.patch, Tez-1631-3.patch, Tez-1631-4.patch, 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)