[
https://issues.apache.org/jira/browse/FLINK-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105220#comment-15105220
]
ASF GitHub Bot commented on FLINK-2935:
---------------------------------------
Github user tillrohrmann commented on a diff in the pull request:
https://github.com/apache/flink/pull/1500#discussion_r49993273
--- Diff: docs/apis/scala_shell.md ---
@@ -69,6 +69,18 @@ Scala-Flink> env.execute("MyProgram")
The Flink Shell comes with command history and autocompletion.
+## Scala Shell with Flink on YARN
+
+The Scala shell can connect Flink cluster on YARN. To connect deployed
Flink cluster on YARN, use following command:
+
+~~~bash
+bin/start-scala-shell.sh yarn
+~~~
+
+The shell reads the connection information of the deployed Flink cluster
from a `.yarn-properties` file in temporary directory. If there is no deployed
Flink cluster on YARN, the shell prints error message.
+
+The shell can deploy Flink cluster to YARN for the shell only. If you add
an parameter `-n <arg>` which means a number of containers, the shell deploy a
new Flink cluster on YARN and connect the cluster. You can also specify options
for YARN cluster such as memory for JobManager, name of YARN application, etc..
--- End diff --
deploy *a* Flink cluster to YARN, *which is used exclusively by the shell*.
> Allow scala shell to read yarn properties
> -----------------------------------------
>
> Key: FLINK-2935
> URL: https://issues.apache.org/jira/browse/FLINK-2935
> Project: Flink
> Issue Type: Improvement
> Components: Scala Shell
> Affects Versions: 0.9.1
> Reporter: Johannes
> Assignee: Chiwan Park
> Priority: Minor
> Labels: easyfix
>
> Currently the deployment of flink via yarn and the scala shell are not linked.
> When deploying a yarn session the file
> bq. org.apache.flink.client.CliFrontend
> creates a
> bq. .yarn-properties-$username
> file with the connection properties.
> There should be a way to have the scala shell automatically read this file if
> wanted as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
