[
https://issues.apache.org/jira/browse/FLINK-5903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15946691#comment-15946691
]
ASF GitHub Bot commented on FLINK-5903:
---------------------------------------
Github user WangTaoTheTonic commented on the issue:
https://github.com/apache/flink/pull/3408
All right. That makes sense. Let me rephrase that and please check if we
are in same channel:
1. slots of taskmanager is decided by `-s/-ys` and
`taskmanager.numberOfTaskSlots`, the former has higher priority; and
2. the vcores of yarn container is decided by `yarn.containers.vcores`,
which will use values of `-s/-ys` or `taskmanager.numberOfTaskSlots` if user
doesn't set `yarn.containers.vcores` explicitly.
Is that right?
> taskmanager.numberOfTaskSlots and yarn.containers.vcores did not work well in
> YARN mode
> ---------------------------------------------------------------------------------------
>
> Key: FLINK-5903
> URL: https://issues.apache.org/jira/browse/FLINK-5903
> Project: Flink
> Issue Type: Sub-task
> Components: YARN
> Reporter: Tao Wang
> Assignee: Tao Wang
> Attachments: set taskmanager.numberOfTaskSlots to 6.JPG, set
> yarn.container.vcores to 5_JM.JPG, set yarn.container.vcores to 5_RM.JPG
>
>
> Now Flink did not respect taskmanager.numberOfTaskSlots and
> yarn.containers.vcores in flink-conf.yaml, but only -s parameter in CLI.
> Details is that taskmanager.numberOfTaskSlots is not working in anyway
> andyarn.containers.vcores is only used in requesting container(TM) resources
> but not aware to TM, which means TM will always think it has default(1) Slots
> if -s is not configured.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
