You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Sachin Goel (JIRA)" <ji...@apache.org> on 2015/10/13 15:38:05 UTC

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

Sachin Goel created FLINK-2850:
----------------------------------

             Summary: 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: Bug
            Reporter: 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)