kl0u commented on a change in pull request #12549:
URL: https://github.com/apache/flink/pull/12549#discussion_r437925003
##########
File path: docs/ops/deployment/yarn_setup.md
##########
@@ -251,6 +250,31 @@ The user-jars position in the class path can be controlled
by setting the parame
- `FIRST`: Adds the jar to the beginning of the system class path.
- `LAST`: Adds the jar to the end of the system class path.
+## Run an application in Application Mode
+
+To launch an application in [Application Mode]({% link ops/deployment/index.md
%}#deployment-modes), you can type:
+
+{% highlight bash %}
+./bin/flink run-application -t yarn-application ./examples/batch/WordCount.jar
+{% endhighlight %}
+
+<div class="alert alert-info" markdown="span">
+ <strong>Attention:</strong> Apart from the `-t`, all other configuration
parameters, such as the path
+ to the savepoint to be used to bootstrap the application's state, the
application parallelism or the
+ required job manager/task manager memory sizes, can be specified by their
configuration option,
+ prefixed by `-D`.
+</div>
+
+As an example, the command to specify the memory sizes of the JM and the TM,
looks like:
+
+{% highlight bash %}
+./bin/flink run-application -t yarn-application
-Djobmanager.memory.process.size=2048m -Dtaskmanager.memory.process.size=4096m
./examples/batch/WordCount.jar
+{% endhighlight %}
+
Review comment:
I agree that the interplay between the application mode and the new
configurations is where the real potential of the application mode lie, but
given that these configurations are not unique to the application mode, I was
planning to put them in another place where we have sth like "Best Practices".
I can, though, include a sentence that points to the new parameters and says
that the combination of all oh these allows for almost zero cost job submission.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
