You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Maximilian Michels (JIRA)" <ji...@apache.org> on 2015/10/26 13:55:27 UTC

[jira] [Updated] (FLINK-2850) Limit the types of jobs which can run in detached mode

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

Maximilian Michels updated FLINK-2850:
--------------------------------------
    Issue Type: Sub-task  (was: Bug)
        Parent: FLINK-2797

> Limit the types of jobs which can run in detached mode
> ------------------------------------------------------
>
>                 Key: FLINK-2850
>                 URL: https://issues.apache.org/jira/browse/FLINK-2850
>             Project: Flink
>          Issue Type: Sub-task
>            Reporter: Sachin Goel
>            Assignee: Sachin Goel
>
> Currently, there are two types of programs which can be submitted.
> 1. {{Program}} interface
> 2. Interactive programs, whose {{main}} method is run.
> For interactive mode, 
> In blocking mode, the programs can be executed without any issues since every execution is blocked, and its results can be made available at a further point in the program, as well as the {{Client}} is kept alive and is able to receive job outputs.
> However, in detached mode, interactive programs which are any of the following three types of programs create issues:
> 1. {code}
> DataSet<T> dataset = ...
> List<T> result = dataset.collect(); // accesses accumulators but the results of the inner call to execute aren't available
> {code}
> 2. {code}
> env.execute().getAccumulatorResult(); // fails again because the results aren't availabe.
> {code}
> 3.
> {code}
> env.execute();
> env.execute(); // two executions. Will return two different job ids
> {code}
> These problems make the current yarn detached job mode fail, and will lead to issues when fixing FLINK-2797.



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