Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Fri, 28 Aug 2015 12:37:45 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: issues@flink.apache.org
Message-ID: <JIRA.12833719.1432890296000.193591.1440765465910@Atlassian.JIRA>
In-Reply-To: <JIRA.12833719.1432890296000@Atlassian.JIRA>
References: <JIRA.12833719.1432890296000@Atlassian.JIRA>
 <JIRA.12833719.1432890296612@arcas>
Subject: [jira] [Commented] (FLINK-2111) Add "stop" signal to cleanly
 shutdown streaming jobs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Github user tillrohrmann commented on a diff in the pull request:

    https://github.com/apache/flink/pull/750#discussion_r38195178
  
    --- Diff: flink-runtime/src/test/java/org/apache/flink/runtime/executiongraph/ExecutionGraphConstructionTest.java ---
    @@ -450,8 +414,8 @@ private void verifyTestGraph(ExecutionGraph eg, JobID jobId,
     		}
     	}
     	
    -	@Test
    -	public void testCannotConnectMissingId() {
    +	@Test(expected = JobException.class)
    +	public void testCannotConnectMissingId() throws JobException {
    --- End diff --
    
    That makes sense. Thanks for clarifying :-)


> Add "stop" signal to cleanly shutdown streaming jobs
> ----------------------------------------------------
>
>                 Key: FLINK-2111
>                 URL: https://issues.apache.org/jira/browse/FLINK-2111
>             Project: Flink
>          Issue Type: Improvement
>          Components: Distributed Runtime, JobManager, Local Runtime, Streaming, TaskManager, Webfrontend
>            Reporter: Matthias J. Sax
>            Assignee: Matthias J. Sax
>            Priority: Minor
>
> Currently, streaming jobs can only be stopped using "cancel" command, what is a "hard" stop with no clean shutdown.
> The new introduced "stop" signal, will only affect streaming source tasks such that the sources can stop emitting data and shutdown cleanly, resulting in a clean shutdown of the whole streaming job.
> This feature is a pre-requirment for https://issues.apache.org/jira/browse/FLINK-1929


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