tez-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (TEZ-1631) Session dag submission timeout can result in duplicate DAG submissions
Date Wed, 01 Oct 2014 00:58:34 GMT

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

Bikas Saha updated TEZ-1631:
----------------------------
    Fix Version/s:     (was: 0.4.2)

> 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)

Mime
View raw message