You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2015/10/07 12:31:26 UTC

[jira] [Assigned] (FLINK-2804) Support blocking job submission with Job Manager recovery

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

Till Rohrmann reassigned FLINK-2804:
------------------------------------

    Assignee: Till Rohrmann  (was: Ufuk Celebi)

> Support blocking job submission with Job Manager recovery
> ---------------------------------------------------------
>
>                 Key: FLINK-2804
>                 URL: https://issues.apache.org/jira/browse/FLINK-2804
>             Project: Flink
>          Issue Type: Improvement
>    Affects Versions: 0.10
>            Reporter: Ufuk Celebi
>            Assignee: Till Rohrmann
>            Priority: Minor
>
> Submitting a job in a blocking fashion with JobManager recovery and a failing JobManager fails on the client side (the one submitting the job). The job still continues to be recovered.
> I propose to add simple support to re-retrieve the leading job manager and update the client actor with it and then wait for the result as before.
> As of the current standing in PR #1153 (https://github.com/apache/flink/pull/1153) the job manager assumes that the same actor is running and just keeps on sending execution state updates etc. (if the listening behaviour is not detached).



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