[
https://issues.apache.org/jira/browse/FLINK-8901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16415070#comment-16415070
]
ASF GitHub Bot commented on FLINK-8901:
---------------------------------------
Github user tillrohrmann commented on the issue:
https://github.com/apache/flink/pull/5754
Thanks for the review @NicoK. I will remove the `applicationName` from
`FlinkYarnSessionCli#createDescriptor`.
Technically when you run `bin/flink run -m yarn-cluster`, Flink will also
start a session cluster because you have to support jobs with eager execution
calls like `collect` and `print`.
Merging this PR.
> YARN application name for Flink (per-job) submissions claims it is using only
> 1 TaskManager
> -------------------------------------------------------------------------------------------
>
> Key: FLINK-8901
> URL: https://issues.apache.org/jira/browse/FLINK-8901
> Project: Flink
> Issue Type: Bug
> Components: YARN
> Affects Versions: 1.5.0, 1.6.0
> Reporter: Nico Kruber
> Assignee: Till Rohrmann
> Priority: Blocker
> Labels: flip-6
> Fix For: 1.5.0
>
>
> If (with FLIP-6) a per-job YARN session is created without specifying the
> number of nodes, it will show up as "Flink session with 1 TaskManagers", e.g.
> this job:
> {code}
> ./bin/flink run -m yarn-cluster -yjm 768 -ytm 3072 -ys 2 -p 20 -c
> org.apache.flink.streaming.examples.wordcount.WordCount
> ./examples/streaming/WordCount.jar --input /usr/share/doc/rsync-3.0.6/COPYING
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)