Github user mjsax commented on a diff in the pull request:
https://github.com/apache/flink/pull/750#discussion_r38515501
--- 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 --
I never tried it in a yarn cluster. Do you think it needs special handling?
Basically, the "stop" signal is sent to the JobManager which forward the signal
to all sources. This should be independent if yarn is involved or not. But I
don't have any experience with yarn. Tell me if I am wrong.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
