Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Tue, 16 Feb 2016 14:07:18 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: issues@flink.apache.org
Message-ID: <JIRA.12938904.1455307864000.60703.1455631638094@Atlassian.JIRA>
In-Reply-To: <JIRA.12938904.1455307864000@Atlassian.JIRA>
References: <JIRA.12938904.1455307864000@Atlassian.JIRA>
 <JIRA.12938904.1455307864438@arcas>
Subject: [jira] [Commented] (FLINK-3396) Job submission Savepoint restore
 logic flawed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

ASF GitHub Bot commented on FLINK-3396:
---------------------------------------

Github user uce commented on the pull request:

    https://github.com/apache/flink/pull/1633#issuecomment-184694713
  
    Travis has passed. Did you have another look at this @tillrohrmann?


> Job submission Savepoint restore logic flawed
> ---------------------------------------------
>
>                 Key: FLINK-3396
>                 URL: https://issues.apache.org/jira/browse/FLINK-3396
>             Project: Flink
>          Issue Type: Bug
>            Reporter: Ufuk Celebi
>            Assignee: Ufuk Celebi
>             Fix For: 1.0.0
>
>
> When savepoint restoring fails, the thrown Exception fails the execution graph, but the client is not informed about the failure.
> The expected behaviour is that the submission should be acked with success or failure in any case. With savepoint restore failures, the ack message will be skipped.


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