[
https://issues.apache.org/jira/browse/FLINK-8711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16370018#comment-16370018
]
ASF GitHub Bot commented on FLINK-8711:
---------------------------------------
Github user tillrohrmann commented on the issue:
https://github.com/apache/flink/pull/5532
This is not possible. The problem arises when you start a session cluster
where you don't know the Flink job to submit.
Personally, I'm not a huge fan of too much auto magic which leads to
unexpected behaviour. Instead I would prefer that things fail if not properly
started (e.g. not enough slots) instead of trying to figure out the right
number of slots (which apparently breaks things).
> Flink with YARN uses wrong SlotsPerTaskManager
> ----------------------------------------------
>
> Key: FLINK-8711
> URL: https://issues.apache.org/jira/browse/FLINK-8711
> Project: Flink
> Issue Type: Bug
> Components: YARN
> Affects Versions: 1.3.2, 1.5.0
> Reporter: Aleksandr Filichkin
> Assignee: Till Rohrmann
> Priority: Critical
>
> I see wrong behavior for Flink in YARN.
> I tried to setup SlotsPerTaskManager using "-ys 2 ", but it used only 1 slot.
> I found the code
> [https://github.com/apache/flink/blob/master/flink-yarn/src/main/java/org/apache/flink/yarn/cli/FlinkYarnSessionCli.java#L387]
> For example, when I have :"-yn 7 -ys 2 -p 2" in log I see:
> "The YARN cluster has 14 slots available, but the user requested a
> parallelism of 2 on YARN. Each of the 7 TaskManagers will get 1 slots."
> Why can't we use -ys with -p?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
