You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Jeff Zhang (JIRA)" <ji...@apache.org> on 2014/10/01 02:03:22 UTC
[jira] [Commented] (TEZ-1631) Session dag submission timeout can
result in duplicate DAG submissions
[ https://issues.apache.org/jira/browse/TEZ-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14154058#comment-14154058 ]
Jeff Zhang commented on TEZ-1631:
---------------------------------
bq. This patch looks similar to TEZ-1433-v1.patch on TEZ-1433 right?
Yes
Attach the new patch with unit test refined ( dag successful run in the second submission )
> 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-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)