flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-2804) Support blocking job submission with Job Manager recovery
Date Tue, 06 Oct 2015 12:55:26 GMT

    [ https://issues.apache.org/jira/browse/FLINK-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944986#comment-14944986

ASF GitHub Bot commented on FLINK-2804:

Github user uce commented on the pull request:

    OK, I like your idea! And thanks for finishing it. It depends on the job graph recovery
for the added IT cases to work. I think you can work your way around the tests, but just working
on top of this branch should also work.

> 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: 1.0
>            Reporter: Ufuk Celebi
>            Assignee: Ufuk Celebi
>            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

View raw message