flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maximilian Michels (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FLINK-2850) Limit the types of jobs which can run in detached mode
Date Fri, 13 Nov 2015 15:55:11 GMT

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

Maximilian Michels resolved FLINK-2850.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.0

Fixed in 00e44eda17052c4b3de4f9690c250a45df6f407f

> 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
>             Fix For: 1.0
>
>
> 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)

Mime
View raw message