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

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

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

    https://github.com/apache/flink/pull/750#discussion_r38863884
  
    --- Diff: docs/apis/cli.md ---
    @@ -185,6 +189,18 @@ Action "list" lists running and scheduled programs.
          -s,--scheduled                Show only scheduled programs and their 
JobIDs
     
     
    +Action "stop" stops a running program (streaming jobs only).
    +
    +  Syntax: stop [OPTIONS] <Job ID>
    +  "stop" action options:
    +     -m,--jobmanager <host:port>   Address of the JobManager (master) to 
which
    +                                   to connect. Specify 'yarn-cluster' as 
the
    +                                   JobManager to deploy a YARN cluster for 
the
    +                                   job. Use this flag to connect to a 
different
    --- End diff --
    
    :+1:


> 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)

Reply via email to