You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2018/05/25 16:22:07 UTC
[jira] [Updated] (FLINK-9013) Document yarn.containers.vcores only
being effective when adapting YARN config
[ https://issues.apache.org/jira/browse/FLINK-9013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann updated FLINK-9013:
---------------------------------
Fix Version/s: (was: 1.5.0)
1.5.1
> Document yarn.containers.vcores only being effective when adapting YARN config
> ------------------------------------------------------------------------------
>
> Key: FLINK-9013
> URL: https://issues.apache.org/jira/browse/FLINK-9013
> Project: Flink
> Issue Type: Improvement
> Components: Documentation, YARN
> Affects Versions: 1.5.0
> Reporter: Nico Kruber
> Assignee: Nico Kruber
> Priority: Major
> Fix For: 1.5.1
>
>
> Even after specifying {{yarn.containers.vcores}} and having Flink request such a container from YARN, it may not take these into account at all and return a container with 1 vcore.
> The YARN configuration needs to be adapted to take the vcores into account, e.g. by setting the {{FairScheduler}} in {{yarn-site.xml}}:
> {code}
> <property>
> <name>yarn.resourcemanager.scheduler.class</name>
> <value>org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler</value>
> </property>
> {code}
> This fact should be documented at least at the configuration parameter documentation of {{yarn.containers.vcores}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)