Github user aljoscha commented on a diff in the pull request:
https://github.com/apache/flink/pull/1433#discussion_r46557639
--- Diff: docs/setup/cluster_setup.md ---
@@ -236,34 +236,18 @@ bin/start-cluster.sh
To stop Flink, there is also a `stop-cluster.sh` script.
-
-### Starting Flink in the streaming mode
-
-~~~bash
-bin/start-cluster-streaming.sh
-~~~
-
-The streaming mode changes the startup behavior of Flink: The system is
not
-bringing up the managed memory services with preallocated memory at the
beginning.
-Flink streaming is not using the managed memory employed by the batch
operators.
-By not starting these services with preallocated memory, streaming jobs
can benefit
-from more heap space being available.
-
-Note that you can still start batch jobs in the streaming mode. The memory
manager
-will then allocate memory segments from the Java heap as needed.
-
### Optional: Adding JobManager/TaskManager instances to a cluster
You can add both TaskManager or JobManager instances to your running
cluster with the `bin/taskmanager.sh` and `bin/jobmanager.sh` scripts.
#### Adding a TaskManager
<pre>
-bin/taskmanager.sh (start [batch|streaming])|stop|stop-all)
+bin/taskmanager.sh start|stop|stop-all
</pre>
#### Adding a JobManager
<pre>
-bin/jobmanager.sh (start cluster [batch|streaming])|stop|stop-all)
+bin/jobmanager.sh start|stop|stop-all
--- End diff --
fixed it
---
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.
---
