rmetzger commented on code in PR #29379:
URL: https://github.com/apache/flink/pull/29379#discussion_r4261946310


##########
docs/content/docs/deployment/resource-providers/standalone/overview.md:
##########
@@ -123,6 +123,58 @@ $ ./bin/taskmanager.sh stop
 $ ./bin/standalone-job.sh stop
 ```
 
+### Application Mode in a MiniCluster
+
+An application can also be run with the JobManager and a TaskManager in a 
single process, using the `bin/minicluster.sh` script.
+This is useful for low-throughput jobs where running a separate TaskManager is 
not worth the additional resources.
+The process runs the same components as a distributed application cluster, so 
savepoints, checkpoints, state backends, metrics and the web interface all work 
in the same way.
+
+The script takes the same arguments as `bin/standalone-job.sh`, except that it 
always runs in the foreground (so there is no `start` or `stop`) and arguments 
for the application should be put after `--`:
+
+```bash
+$ ./bin/minicluster.sh --jars 
local://$(pwd)/examples/streaming/TopSpeedWindowing.jar
+```
+
+The web interface is now available at [localhost:8081](http://localhost:8081). 
No TaskManager needs to be started.
+
+The full set of arguments is:
+
+```bash
+$ ./bin/minicluster.sh \
+    [--jars <jar>[,<jar>...]] \
+    [--job-classname <class name>] \
+    [--job-id <job id>] \
+    [--fromSavepoint <path> [--allowNonRestoredState]] \
+    [-D <key>=<value> ...] \
+    [-- <application arguments>]
+```
+
+As with `standalone-job.sh`, if `--jars` is not given, the application is 
loaded from the `usrlib` folder or the classpath.
+
+The MiniCluster has one TaskManager with `taskmanager.numberOfTaskSlots` 
slots, so the parallelism of the application cannot be greater than this.

Review Comment:
   ```suggestion
   The MiniCluster has one TaskManager instance within the JVM with 
`taskmanager.numberOfTaskSlots` slots, so the parallelism of the application 
cannot be greater than this.
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to