Return-Path: X-Original-To: apmail-flink-issues-archive@minotaur.apache.org Delivered-To: apmail-flink-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DB8A218044 for ; Tue, 6 Oct 2015 12:55:35 +0000 (UTC) Received: (qmail 71667 invoked by uid 500); 6 Oct 2015 12:55:26 -0000 Delivered-To: apmail-flink-issues-archive@flink.apache.org Received: (qmail 71609 invoked by uid 500); 6 Oct 2015 12:55:26 -0000 Mailing-List: contact issues-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list issues@flink.apache.org Received: (qmail 71599 invoked by uid 99); 6 Oct 2015 12:55:26 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Oct 2015 12:55:26 +0000 Date: Tue, 6 Oct 2015 12:55:26 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: issues@flink.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (FLINK-2804) Support blocking job submission with Job Manager recovery MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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: https://github.com/apache/flink/pull/1230#issuecomment-145847936 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 (v6.3.4#6332)